Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a6b9121cbaf697aa12c1ee617adaa4106f881e40087b3d3c70e8c000fd6a251

Tx prefix hash: ae8f4f24aa3d077eae74cb73c905d7de4a1747d9408eefcf30bc8b9005ee4e4c
Tx public key: 5ec33699d050ac2bbb98cbaf664e33091289a5c08cb72e9709281ab31624ee53
Timestamp: 1734400046 Timestamp [UCT]: 2024-12-17 01:47:26 Age [y:d:h:m:s]: 00:104:05:32:34
Block: 1176848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74257 RingCT/type: yes/0
Extra: 015ec33699d050ac2bbb98cbaf664e33091289a5c08cb72e9709281ab31624ee530211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9583e20faff0131ddd6327384cc559917a3971a1d8c913ffe916fe5cefb54245 0.600000000000 1663209 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": 1176858, "vin": [ { "gen": { "height": 1176848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9583e20faff0131ddd6327384cc559917a3971a1d8c913ffe916fe5cefb54245" } } ], "extra": [ 1, 94, 195, 54, 153, 208, 80, 172, 43, 187, 152, 203, 175, 102, 78, 51, 9, 18, 137, 165, 192, 140, 183, 46, 151, 9, 40, 26, 179, 22, 36, 238, 83, 2, 17, 0, 0, 0, 6, 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