Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0900dc814b8cc3dae0b244dbb9e7135d18559363f54bac03a92b6d7279a0a718

Tx prefix hash: e8389eb15c1665296dd0ec8dea2d6b6507da6649e8fce9276dfbb49caf7638ce
Tx public key: 727533d8771ac80b9c4f26a724091429d86eef10dfee91bed302e7e9ad24e92d
Timestamp: 1701630924 Timestamp [UCT]: 2023-12-03 19:15:24 Age [y:d:h:m:s]: 01:136:10:04:52
Block: 905264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358660 RingCT/type: yes/0
Extra: 01727533d8771ac80b9c4f26a724091429d86eef10dfee91bed302e7e9ad24e92d02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.614447174000 dcy

stealth address amount amount idx
00: b3fd639ef98777627ea77525950bee28d751614a3c6fbd95be71f13d9c687531 0.614447174000 1362141 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": 905274, "vin": [ { "gen": { "height": 905264 } } ], "vout": [ { "amount": 614447174, "target": { "key": "b3fd639ef98777627ea77525950bee28d751614a3c6fbd95be71f13d9c687531" } } ], "extra": [ 1, 114, 117, 51, 216, 119, 26, 200, 11, 156, 79, 38, 167, 36, 9, 20, 41, 216, 110, 239, 16, 223, 238, 145, 190, 211, 2, 231, 233, 173, 36, 233, 45, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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