Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a446426989e926ea644c463c493d9fcd7b465ea12fedd66b8e6dd9f80bf4966

Tx prefix hash: 9cc0e4fa8fa1d4884eeeb2a4737bfba59c21ba33be3a173e1520dc70f9ee9ea6
Tx public key: dc71f1e04693e4d8c388fe7ad72603dbabaf4e6fe49dabe2d1916f1b94a9ac7f
Timestamp: 1583750249 Timestamp [UCT]: 2020-03-09 10:37:29 Age [y:d:h:m:s]: 04:293:11:37:42
Block: 79052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104817 RingCT/type: yes/0
Extra: 01dc71f1e04693e4d8c388fe7ad72603dbabaf4e6fe49dabe2d1916f1b94a9ac7f021100000001203e3db0000000000000000000

1 output(s) for total of 335.790727420000 dcy

stealth address amount amount idx
00: 0d0f3906efe8f436ba39ddece7e9abf0da5727af53acbffb18c7c40d78a2466e 335.790727420000 144782 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": 79062, "vin": [ { "gen": { "height": 79052 } } ], "vout": [ { "amount": 335790727420, "target": { "key": "0d0f3906efe8f436ba39ddece7e9abf0da5727af53acbffb18c7c40d78a2466e" } } ], "extra": [ 1, 220, 113, 241, 224, 70, 147, 228, 216, 195, 136, 254, 122, 215, 38, 3, 219, 171, 175, 78, 111, 228, 157, 171, 226, 209, 145, 111, 27, 148, 169, 172, 127, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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