Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e84f64c6a50ddc5ce48cc9db9d956403ad6287c4b1fc59dab974d16af71aeb

Tx prefix hash: 4d4a0a31447721ec330e9f4b716b9ce43972192b4d7271d5fc2e20378310443b
Tx public key: aa8f9497316721aee03de3250fdad34f3c04cae4ce9f9b8ca978ee5f423e8e65
Timestamp: 1720427250 Timestamp [UCT]: 2024-07-08 08:27:30 Age [y:d:h:m:s]: 00:279:08:59:21
Block: 1061105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199608 RingCT/type: yes/0
Extra: 01aa8f9497316721aee03de3250fdad34f3c04cae4ce9f9b8ca978ee5f423e8e65021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec798194d634017547db49e0e821dc956c675d3645e653c4bd27071dba4330d 0.600000000000 1531596 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": 1061115, "vin": [ { "gen": { "height": 1061105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec798194d634017547db49e0e821dc956c675d3645e653c4bd27071dba4330d" } } ], "extra": [ 1, 170, 143, 148, 151, 49, 103, 33, 174, 224, 61, 227, 37, 15, 218, 211, 79, 60, 4, 202, 228, 206, 159, 155, 140, 169, 120, 238, 95, 66, 62, 142, 101, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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