Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5019002187ee16700f57062c0c3d21cb69ce0e4c6f07ce742372ddb0e8502c1b

Tx prefix hash: 68e6af81686fa571656c8ebf0e8e1f5ec295e6ac741001697071df3bb1facf9b
Tx public key: dae176b1041b64c54049b3404cb7cad937ad8e8ab0cea04c86f54db5ab5d3697
Timestamp: 1580487657 Timestamp [UCT]: 2020-01-31 16:20:57 Age [y:d:h:m:s]: 04:349:23:12:43
Block: 56047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141212 RingCT/type: yes/0
Extra: 01dae176b1041b64c54049b3404cb7cad937ad8e8ab0cea04c86f54db5ab5d36970211000000012264afe6000000000000000000

1 output(s) for total of 400.215446948000 dcy

stealth address amount amount idx
00: 2d9ba0458dd7927b1967d34af32dae1a336f693fbe1c1d5a9074a1ff339e9c02 400.215446948000 103342 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": 56057, "vin": [ { "gen": { "height": 56047 } } ], "vout": [ { "amount": 400215446948, "target": { "key": "2d9ba0458dd7927b1967d34af32dae1a336f693fbe1c1d5a9074a1ff339e9c02" } } ], "extra": [ 1, 218, 225, 118, 177, 4, 27, 100, 197, 64, 73, 179, 64, 76, 183, 202, 217, 55, 173, 142, 138, 176, 206, 160, 76, 134, 245, 77, 181, 171, 93, 54, 151, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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