Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6bdc63b3c76ef03b3de18bc1da74d3c3dbd771ecb719a5f43d047ff799bad34

Tx prefix hash: 1585937be339029bc1e659b20d82c372020339fa0389238763772f10ecb64196
Tx public key: 1c9a0bdfdf3fa9d6d07840eea239e0e7221c46bb48f5b5af470f32a525ce5484
Timestamp: 1745583431 Timestamp [UCT]: 2025-04-25 12:17:11 Age [y:d:h:m:s]: 00:259:10:45:43
Block: 1269146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183226 RingCT/type: yes/0
Extra: 011c9a0bdfdf3fa9d6d07840eea239e0e7221c46bb48f5b5af470f32a525ce5484021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43ca2b261ababef7f166d680485be7546e5155f1e982758c9e6caa231c6e6fec 0.600000000000 1756381 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": 1269156, "vin": [ { "gen": { "height": 1269146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43ca2b261ababef7f166d680485be7546e5155f1e982758c9e6caa231c6e6fec" } } ], "extra": [ 1, 28, 154, 11, 223, 223, 63, 169, 214, 208, 120, 64, 238, 162, 57, 224, 231, 34, 28, 70, 187, 72, 245, 181, 175, 71, 15, 50, 165, 37, 206, 84, 132, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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