Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9550904dc74b51fcd69d2af78599779558cbcde14734026a700d81617bfd3bd2

Tx prefix hash: 50bcf09e1328ea8a67d4cdb42a351c801852548006a966d2a3d678408cdf0e15
Tx public key: ea9ff7e503961a48df9b72dc1c798f9223e57b31b6d7068edc06ad76907c0db0
Timestamp: 1716488271 Timestamp [UCT]: 2024-05-23 18:17:51 Age [y:d:h:m:s]: 00:306:17:02:45
Block: 1028447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219187 RingCT/type: yes/0
Extra: 01ea9ff7e503961a48df9b72dc1c798f9223e57b31b6d7068edc06ad76907c0db002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e563c95300c915a1d418232bc3a0ea628ced34d5a148e9829e83f4015f3b4d85 0.600000000000 1496440 of 15

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": 1028457, "vin": [ { "gen": { "height": 1028447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e563c95300c915a1d418232bc3a0ea628ced34d5a148e9829e83f4015f3b4d85" } } ], "extra": [ 1, 234, 159, 247, 229, 3, 150, 26, 72, 223, 155, 114, 220, 28, 121, 143, 146, 35, 229, 123, 49, 182, 215, 6, 142, 220, 6, 173, 118, 144, 124, 13, 176, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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