Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111ab39d26f94366f1711f65663e60cd14b4da5eb63f831bda344a890185e7df

Tx prefix hash: 9f7dd8a94bf1727f1e0f542158fd5433df52f82a8d34ee7fbe26f2595c34e62c
Tx public key: bb7f9050e7c32275c01bc1c24a9582647e2c9675e004831a669c5d73c97efc05
Timestamp: 1735811441 Timestamp [UCT]: 2025-01-02 09:50:41 Age [y:d:h:m:s]: 00:166:06:18:43
Block: 1188506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118548 RingCT/type: yes/0
Extra: 01bb7f9050e7c32275c01bc1c24a9582647e2c9675e004831a669c5d73c97efc050211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d505bc6655fc4230c3b64a3f907c202e1bbb3445387b6f7aa6db11928bce74e8 0.600000000000 1675007 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": 1188516, "vin": [ { "gen": { "height": 1188506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d505bc6655fc4230c3b64a3f907c202e1bbb3445387b6f7aa6db11928bce74e8" } } ], "extra": [ 1, 187, 127, 144, 80, 231, 195, 34, 117, 192, 27, 193, 194, 74, 149, 130, 100, 126, 44, 150, 117, 224, 4, 131, 26, 102, 156, 93, 115, 201, 126, 252, 5, 2, 17, 0, 0, 0, 8, 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