Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ad95120293d883a11b4be09a780c3344dc79a3a36dc97265f8963eb325abcaa

Tx prefix hash: c3e6ce521daeacf19c3770399bf70f3f35abb2273a916886b285e986c7be4a9c
Tx public key: 2a0a11ed3e755b76cf3097e91a2747f252022ffc4f4929b1e1f6e8f410c94553
Timestamp: 1702738665 Timestamp [UCT]: 2023-12-16 14:57:45 Age [y:d:h:m:s]: 01:034:20:43:55
Block: 914446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286237 RingCT/type: yes/0
Extra: 012a0a11ed3e755b76cf3097e91a2747f252022ffc4f4929b1e1f6e8f410c9455302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c70cd72e0920a8ea156c3990b040d7b229dd9164bbed57987251d69ac57e06 0.600000000000 1371762 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": 914456, "vin": [ { "gen": { "height": 914446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c70cd72e0920a8ea156c3990b040d7b229dd9164bbed57987251d69ac57e06" } } ], "extra": [ 1, 42, 10, 17, 237, 62, 117, 91, 118, 207, 48, 151, 233, 26, 39, 71, 242, 82, 2, 47, 252, 79, 73, 41, 177, 225, 246, 232, 244, 16, 201, 69, 83, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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