Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 467a885c4d7d190e488ef7697eb09a28f654289300d3ed72abeb40172418f0de

Tx prefix hash: 2f0a3a73910d60c484c01d89f3130d0afa51d7095441e5ff33ad7beba6b27a2e
Tx public key: 0a5288ad6de3121f6fb7f798095c2cc3062e67eaac67a8ec1857370d729a6a22
Timestamp: 1735024417 Timestamp [UCT]: 2024-12-24 07:13:37 Age [y:d:h:m:s]: 00:107:18:40:23
Block: 1182005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76810 RingCT/type: yes/0
Extra: 010a5288ad6de3121f6fb7f798095c2cc3062e67eaac67a8ec1857370d729a6a220211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ffd1f6565dc865dfbf1967970f7dfb639b4e2a1d5fd175c52fb67a564735b44 0.600000000000 1668434 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": 1182015, "vin": [ { "gen": { "height": 1182005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ffd1f6565dc865dfbf1967970f7dfb639b4e2a1d5fd175c52fb67a564735b44" } } ], "extra": [ 1, 10, 82, 136, 173, 109, 227, 18, 31, 111, 183, 247, 152, 9, 92, 44, 195, 6, 46, 103, 234, 172, 103, 168, 236, 24, 87, 55, 13, 114, 154, 106, 34, 2, 17, 0, 0, 0, 2, 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