Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543fd9dc1805901546fc8b5d3c7f29076f15e89b1ef892f159cfa9a70c433f42

Tx prefix hash: 3f2ed54c61b9cb4a30362430897311b458bbcf5d2f1e9bdad08f23eb2f4fdc02
Tx public key: 785b56cac9a41e4b97de590feae48cb22be6ec099a720f66d88d4ae0d33b1fca
Timestamp: 1737456617 Timestamp [UCT]: 2025-01-21 10:50:17 Age [y:d:h:m:s]: 00:148:15:21:09
Block: 1202086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105953 RingCT/type: yes/0
Extra: 01785b56cac9a41e4b97de590feae48cb22be6ec099a720f66d88d4ae0d33b1fca0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 318e30c6141deb0de4e1865bb4c33b2713fcf2c57c44ddc8761c012f23e303ea 0.600000000000 1688745 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": 1202096, "vin": [ { "gen": { "height": 1202086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "318e30c6141deb0de4e1865bb4c33b2713fcf2c57c44ddc8761c012f23e303ea" } } ], "extra": [ 1, 120, 91, 86, 202, 201, 164, 30, 75, 151, 222, 89, 15, 234, 228, 140, 178, 43, 230, 236, 9, 154, 114, 15, 102, 216, 141, 74, 224, 211, 59, 31, 202, 2, 17, 0, 0, 0, 4, 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