Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 302c50da2120a8f80bb29cf90ebd67eb85cd76d3fc3215de415d501d1ab2223d

Tx prefix hash: 6efa4fb6282841ddcfc9d36184381c8649a54586f9c668dbf33484a3d67582b9
Tx public key: 0e1ef0b0657ed620be2cd6fb0d41670a90e13f28cb3e7496c23fc7088b6cd704
Timestamp: 1702569522 Timestamp [UCT]: 2023-12-14 15:58:42 Age [y:d:h:m:s]: 01:353:03:32:55
Block: 913046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511277 RingCT/type: yes/0
Extra: 010e1ef0b0657ed620be2cd6fb0d41670a90e13f28cb3e7496c23fc7088b6cd70402110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86a89e9b78dc033153daad1174b1b83fb676c3859f5de3119e0f98597a8f9fcc 0.600000000000 1370288 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": 913056, "vin": [ { "gen": { "height": 913046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86a89e9b78dc033153daad1174b1b83fb676c3859f5de3119e0f98597a8f9fcc" } } ], "extra": [ 1, 14, 30, 240, 176, 101, 126, 214, 32, 190, 44, 214, 251, 13, 65, 103, 10, 144, 225, 63, 40, 203, 62, 116, 150, 194, 63, 199, 8, 139, 108, 215, 4, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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