Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4b58f3e1f3d435e36cf62bc7b1c97411a3182e63cc74f12d3c4dd5ebdc1f66

Tx prefix hash: 3a3c492bbbdb08245c1b02ddcaf834fec80eb4cfd45651de38d7cb45eade9133
Tx public key: ffe6c02304e6d25ef4cef29105a51b77d634eaa2ab312ac8539e98eafc28ef87
Timestamp: 1685318038 Timestamp [UCT]: 2023-05-28 23:53:58 Age [y:d:h:m:s]: 01:236:02:31:33
Block: 770279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430131 RingCT/type: yes/0
Extra: 01ffe6c02304e6d25ef4cef29105a51b77d634eaa2ab312ac8539e98eafc28ef87021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.720862173000 dcy

stealth address amount amount idx
00: d92efbf545d2872e96ac2ce07ca0a8febca576234553a4b4f09cec5f62256055 1.720862173000 1219578 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": 770289, "vin": [ { "gen": { "height": 770279 } } ], "vout": [ { "amount": 1720862173, "target": { "key": "d92efbf545d2872e96ac2ce07ca0a8febca576234553a4b4f09cec5f62256055" } } ], "extra": [ 1, 255, 230, 192, 35, 4, 230, 210, 94, 244, 206, 242, 145, 5, 165, 27, 119, 214, 52, 234, 162, 171, 49, 42, 200, 83, 158, 152, 234, 252, 40, 239, 135, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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