Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6492d54ab7aabce3e15dd0beab0ddaa269184c8fd4152fefcd95839048c63e2

Tx prefix hash: 618e65e1f0e63f3077b81f85a0ab1c91a1b8da874e9ffec84b9c49c5bd0e8a84
Tx public key: f7ad14fe9a51a22fc02828f88730666d522d5643e738c728232b1575e0bf23bf
Timestamp: 1576424652 Timestamp [UCT]: 2019-12-15 15:44:12 Age [y:d:h:m:s]: 05:056:15:23:12
Block: 27461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187169 RingCT/type: yes/0
Extra: 01f7ad14fe9a51a22fc02828f88730666d522d5643e738c728232b1575e0bf23bf0211000000279159db1e000000000000000000

1 output(s) for total of 497.749890778000 dcy

stealth address amount amount idx
00: a0ea29bc74f75890230f4f4b5af27ae987d74970b2868699611f6ef7e5c2dbea 497.749890778000 45463 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": 27471, "vin": [ { "gen": { "height": 27461 } } ], "vout": [ { "amount": 497749890778, "target": { "key": "a0ea29bc74f75890230f4f4b5af27ae987d74970b2868699611f6ef7e5c2dbea" } } ], "extra": [ 1, 247, 173, 20, 254, 154, 81, 162, 47, 192, 40, 40, 248, 135, 48, 102, 109, 82, 45, 86, 67, 231, 56, 199, 40, 35, 43, 21, 117, 224, 191, 35, 191, 2, 17, 0, 0, 0, 39, 145, 89, 219, 30, 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