Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e1db771b1c7221b8bdaade05905f80dc8789da0375897e8f7e34af36f869334

Tx prefix hash: 2b438d2f218bc6f226a3d6aead2e25fb990ac6934f4d2a2e1c88eb09b45c99fe
Tx public key: bbaf8290b614e040c9d3382ded3d60e447baf84acbefbf0f9941b1ab55629c59
Timestamp: 1673605183 Timestamp [UCT]: 2023-01-13 10:19:43 Age [y:d:h:m:s]: 02:096:04:22:55
Block: 673781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590428 RingCT/type: yes/0
Extra: 01bbaf8290b614e040c9d3382ded3d60e447baf84acbefbf0f9941b1ab55629c590211000000018b7b6602000000000000000000

1 output(s) for total of 3.593219922000 dcy

stealth address amount amount idx
00: b0bd726e4f0d4c4b8409c12e7c0f2661514fa980d304d9c4acc04c2622f1d1d2 3.593219922000 1115406 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": 673791, "vin": [ { "gen": { "height": 673781 } } ], "vout": [ { "amount": 3593219922, "target": { "key": "b0bd726e4f0d4c4b8409c12e7c0f2661514fa980d304d9c4acc04c2622f1d1d2" } } ], "extra": [ 1, 187, 175, 130, 144, 182, 20, 224, 64, 201, 211, 56, 45, 237, 61, 96, 228, 71, 186, 248, 74, 203, 239, 191, 15, 153, 65, 177, 171, 85, 98, 156, 89, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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