Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 884f2e082177d0215e9720f4a541fd34d9a63cfa101fe74f7563e8a0ebcb1581

Tx prefix hash: cb6d22ca9775fdf5338fa77f9cadae89dc42814b6824932f1f2791b4736a310d
Tx public key: 1c3a9e61cc8b392401800f7f61bf4659395ab756240aa0fbd56b3c937f0de028
Timestamp: 1762617573 Timestamp [UCT]: 2025-11-08 15:59:33 Age [y:d:h:m:s]: 00:043:19:32:12
Block: 1407754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31364 RingCT/type: yes/0
Extra: 011c3a9e61cc8b392401800f7f61bf4659395ab756240aa0fbd56b3c937f0de028021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf0680e1658a2904db07504d72fee88d1d77efc9a0cfc888db36b0a9c5f7699e 0.600000000000 1896175 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": 1407764, "vin": [ { "gen": { "height": 1407754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf0680e1658a2904db07504d72fee88d1d77efc9a0cfc888db36b0a9c5f7699e" } } ], "extra": [ 1, 28, 58, 158, 97, 204, 139, 57, 36, 1, 128, 15, 127, 97, 191, 70, 89, 57, 90, 183, 86, 36, 10, 160, 251, 213, 107, 60, 147, 127, 13, 224, 40, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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