Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351c405df9d6db6bcfdd59ea0ab1fda4bb4df44869cc9445b6091f262726986f

Tx prefix hash: 3b045e697b6dc7bac45f710cf02cc6cc12ee610a710e76d8122164e9fd225a6d
Tx public key: 174612d0e8341bbdd3c23651a9f0ce7c873bdd55c85efc90e13afe9bae03d0e8
Timestamp: 1751030075 Timestamp [UCT]: 2025-06-27 13:14:35 Age [y:d:h:m:s]: 00:215:03:32:28
Block: 1313865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151727 RingCT/type: yes/0
Extra: 01174612d0e8341bbdd3c23651a9f0ce7c873bdd55c85efc90e13afe9bae03d0e8021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65d9ab8a0d78812d628daf5c0338f8498f080ee787e3a03a9d8d02c5c3f7a6f2 0.600000000000 1801508 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": 1313875, "vin": [ { "gen": { "height": 1313865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d9ab8a0d78812d628daf5c0338f8498f080ee787e3a03a9d8d02c5c3f7a6f2" } } ], "extra": [ 1, 23, 70, 18, 208, 232, 52, 27, 189, 211, 194, 54, 81, 169, 240, 206, 124, 135, 59, 221, 85, 200, 94, 252, 144, 225, 58, 254, 155, 174, 3, 208, 232, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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