Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739a77ba58ae7034d3ca0028f55adc6009f676362a4c89a998a3c32a351d6b7c

Tx prefix hash: 98a21f4309d36dadd7f5ab791eba1644bc9e32b92863d2194c7451dd4cf07ec3
Tx public key: 42d355bf6cf8a6ecedd6d3af9384980ecd47fafb77b616fdb65c121e963fe8cf
Timestamp: 1713415068 Timestamp [UCT]: 2024-04-18 04:37:48 Age [y:d:h:m:s]: 01:205:05:53:54
Block: 1002946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405358 RingCT/type: yes/0
Extra: 0142d355bf6cf8a6ecedd6d3af9384980ecd47fafb77b616fdb65c121e963fe8cf0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cca8bc9603fdc9cc5b8bd70e3ff60fa4f40cec520329f69d0ca5d6ecf0f991a6 0.600000000000 1463476 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": 1002956, "vin": [ { "gen": { "height": 1002946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cca8bc9603fdc9cc5b8bd70e3ff60fa4f40cec520329f69d0ca5d6ecf0f991a6" } } ], "extra": [ 1, 66, 211, 85, 191, 108, 248, 166, 236, 237, 214, 211, 175, 147, 132, 152, 14, 205, 71, 250, 251, 119, 182, 22, 253, 182, 92, 18, 30, 150, 63, 232, 207, 2, 17, 0, 0, 0, 5, 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