Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3c406941a7c6bb22cde5e2ec6be808dca8a2dc2b38e8337d7d3d6056ca8172e9

Tx prefix hash: 9610a2c32540d567adeb078c0606cd7e921b426790d8b63d5d45769dd4ba2f11
Tx public key: 97652b5b6d48f926ec2250485684f2c10d1542a319849522c29cf970fe88efb9
Timestamp: 1694887454 Timestamp [UCT]: 2023-09-16 18:04:14 Age [y:d:h:m:s]: 01:204:22:08:44
Block: 849551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407547 RingCT/type: yes/0
Extra: 0197652b5b6d48f926ec2250485684f2c10d1542a319849522c29cf970fe88efb902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.939907097000 dcy

stealth address amount amount idx
00: 44dfae4b13525c394d3cd447f5b82aba2335a6f00ab28dfe165c7ca63748506f 0.939907097000 1303221 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 849561, "vin": [ { "gen": { "height": 849551 } } ], "vout": [ { "amount": 939907097, "target": { "key": "44dfae4b13525c394d3cd447f5b82aba2335a6f00ab28dfe165c7ca63748506f" } } ], "extra": [ 1, 151, 101, 43, 91, 109, 72, 249, 38, 236, 34, 80, 72, 86, 132, 242, 193, 13, 21, 66, 163, 25, 132, 149, 34, 194, 156, 249, 112, 254, 136, 239, 185, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8