Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472f33541e20abdf452f9efe6abfa6f19bc2fa3f75c3b83ca404dd258aaf8716

Tx prefix hash: 9ef3a2d2e57cfd7690fcf99f792a418e081d4b09417d9eb468c02a0c6da9f7c6
Tx public key: afc4183f230cb6280bf2640a4b8c50fd54c4c8cd16f4b12338a66ac8c3f8a9f7
Timestamp: 1762983005 Timestamp [UCT]: 2025-11-12 21:30:05 Age [y:d:h:m:s]: 00:014:12:50:01
Block: 1410777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10412 RingCT/type: yes/0
Extra: 01afc4183f230cb6280bf2640a4b8c50fd54c4c8cd16f4b12338a66ac8c3f8a9f7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c95666327f93ba2681c3138f711c02f917f1488922ca85c952e1c17bdec3c077 0.600000000000 1899230 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": 1410787, "vin": [ { "gen": { "height": 1410777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c95666327f93ba2681c3138f711c02f917f1488922ca85c952e1c17bdec3c077" } } ], "extra": [ 1, 175, 196, 24, 63, 35, 12, 182, 40, 11, 242, 100, 10, 75, 140, 80, 253, 84, 196, 200, 205, 22, 244, 177, 35, 56, 166, 106, 200, 195, 248, 169, 247, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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