Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528a39c4fe52950a255b011ff92b57718983a1166a00717c1af45fcc15f5aec6

Tx prefix hash: a41e1267e220ef564c4e9e63a41655528146c386e4d85a6aaed6d87be10f8838
Tx public key: 4d305956ec5b896e3f54c41e96c2c3ec2d09f9fa572eda957309a2a237fda2a4
Timestamp: 1758219626 Timestamp [UCT]: 2025-09-18 18:20:26 Age [y:d:h:m:s]: 00:111:09:12:53
Block: 1371303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79759 RingCT/type: yes/0
Extra: 014d305956ec5b896e3f54c41e96c2c3ec2d09f9fa572eda957309a2a237fda2a4021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17159ae432e1d352798b1e3f960ea2827a85666885aa4b4ccab1f1214004865d 0.600000000000 1859380 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": 1371313, "vin": [ { "gen": { "height": 1371303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17159ae432e1d352798b1e3f960ea2827a85666885aa4b4ccab1f1214004865d" } } ], "extra": [ 1, 77, 48, 89, 86, 236, 91, 137, 110, 63, 84, 196, 30, 150, 194, 195, 236, 45, 9, 249, 250, 87, 46, 218, 149, 115, 9, 162, 162, 55, 253, 162, 164, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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