Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f00351d9e2f8831c4e089b6a81612016992837de927574cbe886fd32a61997d

Tx prefix hash: d59d37b3cca2d926c557ee2d3877d14f3abfa0c4111acc63caac75f834b4c4d5
Tx public key: 00c6e21aacbff1a1c7fab731c930fc899166e843a0d0e1639ed3318b90b7d5d6
Timestamp: 1755027762 Timestamp [UCT]: 2025-08-12 19:42:42 Age [y:d:h:m:s]: 00:105:18:35:48
Block: 1345662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74926 RingCT/type: yes/0
Extra: 0100c6e21aacbff1a1c7fab731c930fc899166e843a0d0e1639ed3318b90b7d5d6021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbdaa3292e36007ac6090fec85518e7a0e6e3401bac5925bd1357f321c170609 0.600000000000 1833557 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": 1345672, "vin": [ { "gen": { "height": 1345662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbdaa3292e36007ac6090fec85518e7a0e6e3401bac5925bd1357f321c170609" } } ], "extra": [ 1, 0, 198, 226, 26, 172, 191, 241, 161, 199, 250, 183, 49, 201, 48, 252, 137, 145, 102, 232, 67, 160, 208, 225, 99, 158, 211, 49, 139, 144, 183, 213, 214, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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