Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0317305a8f39dadb2bdcafa62bb2d7f0b60529f59e23a730a4e41188b640a3

Tx prefix hash: 9a3aff75b53b1e81cd396edc977715f9687663a9d51835c1582c034d61e9f21f
Tx public key: cc2932d2a3cf7544bd4c02d8b69f6d19bc1629492c30f6f011117434f202aa99
Timestamp: 1730594170 Timestamp [UCT]: 2024-11-03 00:36:10 Age [y:d:h:m:s]: 00:079:23:16:13
Block: 1145293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57182 RingCT/type: yes/0
Extra: 01cc2932d2a3cf7544bd4c02d8b69f6d19bc1629492c30f6f011117434f202aa990211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25ffb4137188fb75d1f2a34a1f77a16f3f65c5ffaa42370d676be769176ef05c 0.600000000000 1629702 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": 1145303, "vin": [ { "gen": { "height": 1145293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25ffb4137188fb75d1f2a34a1f77a16f3f65c5ffaa42370d676be769176ef05c" } } ], "extra": [ 1, 204, 41, 50, 210, 163, 207, 117, 68, 189, 76, 2, 216, 182, 159, 109, 25, 188, 22, 41, 73, 44, 48, 246, 240, 17, 17, 116, 52, 242, 2, 170, 153, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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