Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c43c45381f70b04cfe15d5437673a1f6ba42f8e6036e174542f6f5e7e10412

Tx prefix hash: a2a3210e049c75c0b603b3d8fbd93ee1bdeb2321106aac2d0dd19c7e3043c2eb
Tx public key: e9afa0ee25d6fc73af48ae9d1903c9a09e9f19dec52ce83940b142fa19df62cd
Timestamp: 1581091837 Timestamp [UCT]: 2020-02-07 16:10:37 Age [y:d:h:m:s]: 04:321:22:01:33
Block: 60730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121485 RingCT/type: yes/0
Extra: 01e9afa0ee25d6fc73af48ae9d1903c9a09e9f19dec52ce83940b142fa19df62cd02110000000456c366d3000000000000000000

1 output(s) for total of 386.168741696000 dcy

stealth address amount amount idx
00: 1192ac007c1a1de7cdff487df16d87751716cfe446be86742ae0088b30f49317 386.168741696000 111797 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": 60740, "vin": [ { "gen": { "height": 60730 } } ], "vout": [ { "amount": 386168741696, "target": { "key": "1192ac007c1a1de7cdff487df16d87751716cfe446be86742ae0088b30f49317" } } ], "extra": [ 1, 233, 175, 160, 238, 37, 214, 252, 115, 175, 72, 174, 157, 25, 3, 201, 160, 158, 159, 25, 222, 197, 44, 232, 57, 64, 177, 66, 250, 25, 223, 98, 205, 2, 17, 0, 0, 0, 4, 86, 195, 102, 211, 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