Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3ca7e71ca8f7ff0d605ede6b2321b434ba84bea755b3bf85319efd12c9f572a

Tx prefix hash: e5c588cc996590f8514ab7ad5418dd9009e3144b5af4ec32feaa3be0724ad451
Tx public key: c052440e12423cd26396d9bb8587aae79ae588be79b5c16b03bade7cfb26daaf
Timestamp: 1580619937 Timestamp [UCT]: 2020-02-02 05:05:37 Age [y:d:h:m:s]: 04:331:09:13:41
Block: 56873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128183 RingCT/type: yes/0
Extra: 01c052440e12423cd26396d9bb8587aae79ae588be79b5c16b03bade7cfb26daaf021100000001391a8d0e000000000000000000

1 output(s) for total of 397.701258062000 dcy

stealth address amount amount idx
00: 1ddd44eeb11122f2068e41c3ba4b0571918144c98ee4dbc5fd41e11fca0c2d38 397.701258062000 104880 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": 56883, "vin": [ { "gen": { "height": 56873 } } ], "vout": [ { "amount": 397701258062, "target": { "key": "1ddd44eeb11122f2068e41c3ba4b0571918144c98ee4dbc5fd41e11fca0c2d38" } } ], "extra": [ 1, 192, 82, 68, 14, 18, 66, 60, 210, 99, 150, 217, 187, 133, 135, 170, 231, 154, 229, 136, 190, 121, 181, 193, 107, 3, 186, 222, 124, 251, 38, 218, 175, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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