Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a547da4c21e07cd8e60f7ea11e7e451ed996266762b3c7faa4d9230c43ab6095

Tx prefix hash: bd5b86ee7a339b5ab1fbd13631156dfa6db5358e33103d8f4b8a529197e23af6
Tx public key: 14e9c27067ef615f8ffc6aaf50b8f855f5e2a9ef89b02303c7f5e56ff631a2c6
Timestamp: 1731498732 Timestamp [UCT]: 2024-11-13 11:52:12 Age [y:d:h:m:s]: 00:156:13:05:43
Block: 1152797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111712 RingCT/type: yes/0
Extra: 0114e9c27067ef615f8ffc6aaf50b8f855f5e2a9ef89b02303c7f5e56ff631a2c60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f560fd34951df1eea00ce05f22510f90782ff31e6d74eaeb496c3a1060e2e1e 0.600000000000 1638400 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": 1152807, "vin": [ { "gen": { "height": 1152797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f560fd34951df1eea00ce05f22510f90782ff31e6d74eaeb496c3a1060e2e1e" } } ], "extra": [ 1, 20, 233, 194, 112, 103, 239, 97, 95, 143, 252, 106, 175, 80, 184, 248, 85, 245, 226, 169, 239, 137, 176, 35, 3, 199, 245, 229, 111, 246, 49, 162, 198, 2, 17, 0, 0, 0, 3, 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