Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c91da9d112fad00dd7cc4da9916c7ca12ca106e4bacfccfac9469912890d8cb1

Tx prefix hash: dd697ca124930e0ebde6095357e06c6d4249909743de196c84a849fb3c22ac4b
Tx public key: 68788263a9f8e2840a8116612d4427e319f5d0c5a54dd25e0cd8b584e8c38084
Timestamp: 1731435606 Timestamp [UCT]: 2024-11-12 18:20:06 Age [y:d:h:m:s]: 00:015:08:19:03
Block: 1152270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10984 RingCT/type: yes/0
Extra: 0168788263a9f8e2840a8116612d4427e319f5d0c5a54dd25e0cd8b584e8c38084021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a25667d59f31e931cb73852202d3c3671a9ab776d5fc620e678ed039476df7c 0.600000000000 1637865 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": 1152280, "vin": [ { "gen": { "height": 1152270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a25667d59f31e931cb73852202d3c3671a9ab776d5fc620e678ed039476df7c" } } ], "extra": [ 1, 104, 120, 130, 99, 169, 248, 226, 132, 10, 129, 22, 97, 45, 68, 39, 227, 25, 245, 208, 197, 165, 77, 210, 94, 12, 216, 181, 132, 232, 195, 128, 132, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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