Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395c164fa8bef23a47e68a03c4148f5edce3d5f194b053c9c98604399bc14646

Tx prefix hash: 89d93713eb8df6063c21b9d0539f5ae7b52de579aa3f3a870bf0145e1f72f438
Tx public key: 9f03edfc5a1bfc6553da03a62c46b6e6fc657f382edaeb47e6182b9e2c1e6937
Timestamp: 1764345372 Timestamp [UCT]: 2025-11-28 15:56:12 Age [y:d:h:m:s]: 00:039:22:47:43
Block: 1422070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28608 RingCT/type: yes/0
Extra: 019f03edfc5a1bfc6553da03a62c46b6e6fc657f382edaeb47e6182b9e2c1e6937021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c29f54c81d9bf6313136450e4b9eccd30b081fb778ef959da2980c6381dd2573 0.600000000000 1910635 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": 1422080, "vin": [ { "gen": { "height": 1422070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c29f54c81d9bf6313136450e4b9eccd30b081fb778ef959da2980c6381dd2573" } } ], "extra": [ 1, 159, 3, 237, 252, 90, 27, 252, 101, 83, 218, 3, 166, 44, 70, 182, 230, 252, 101, 127, 56, 46, 218, 235, 71, 230, 24, 43, 158, 44, 30, 105, 55, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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