Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a78b9a958fe59444637ad347484cb5fe219cdc89f11dabdaef1d727b21a9e10c

Tx prefix hash: 245a623495366c0839bf47e035bee36a605f5ec4617743d751d7babe90011b3c
Tx public key: 5350bdbe24f2b7af80b136fc4d0f8dc7484c97db7c5f98bf114eed7b1c4d6b11
Timestamp: 1706379580 Timestamp [UCT]: 2024-01-27 18:19:40 Age [y:d:h:m:s]: 01:029:08:43:30
Block: 944615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282032 RingCT/type: yes/0
Extra: 015350bdbe24f2b7af80b136fc4d0f8dc7484c97db7c5f98bf114eed7b1c4d6b110211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 508f0077ade2ec04cc0c34855fc326bf3fc5e1a8eea011789d94aa5ac90b427d 0.600000000000 1402899 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": 944625, "vin": [ { "gen": { "height": 944615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "508f0077ade2ec04cc0c34855fc326bf3fc5e1a8eea011789d94aa5ac90b427d" } } ], "extra": [ 1, 83, 80, 189, 190, 36, 242, 183, 175, 128, 177, 54, 252, 77, 15, 141, 199, 72, 76, 151, 219, 124, 95, 152, 191, 17, 78, 237, 123, 28, 77, 107, 17, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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