Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36ca3165dd32b6892dd8e821953d1def702bb26f971da192ae721986df3d55ed

Tx prefix hash: 8cfc3ce0efe3546cb1554ddaf7caf57ba5dd78678e8001c7512a851d961268f6
Tx public key: d2664cfe3f85f9ff12dfb989e812652b580e27f30b1d54967a099f1046d22999
Timestamp: 1736617783 Timestamp [UCT]: 2025-01-11 17:49:43 Age [y:d:h:m:s]: 00:157:23:23:01
Block: 1195182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112611 RingCT/type: yes/0
Extra: 01d2664cfe3f85f9ff12dfb989e812652b580e27f30b1d54967a099f1046d2299902110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ae97b869a6b22b1b9ebfa88afc965c6e9f5f378f67a805c06d7dc61373fbc0 0.600000000000 1681771 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": 1195192, "vin": [ { "gen": { "height": 1195182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ae97b869a6b22b1b9ebfa88afc965c6e9f5f378f67a805c06d7dc61373fbc0" } } ], "extra": [ 1, 210, 102, 76, 254, 63, 133, 249, 255, 18, 223, 185, 137, 232, 18, 101, 43, 88, 14, 39, 243, 11, 29, 84, 150, 122, 9, 159, 16, 70, 210, 41, 153, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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