Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b167b72c2c1c2c1d0013779622e4b5d2db01e86e7af9a5e2881d14cc6bf816

Tx prefix hash: 24633b415c977d81c6798856939bd7b80a0024cecd28a23fa42c0fb9ce3b85b8
Tx public key: 65e521d0a6641abc0987fa3ef0602e49ee8753a3c220fa51527a1ce2ad2374a2
Timestamp: 1755278693 Timestamp [UCT]: 2025-08-15 17:24:53 Age [y:d:h:m:s]: 00:129:17:05:34
Block: 1347333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92462 RingCT/type: yes/0
Extra: 0165e521d0a6641abc0987fa3ef0602e49ee8753a3c220fa51527a1ce2ad2374a20211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99eae5ed5fd8ed9734c20defb2994bf6d29cbae26a1eb71bfc16c27fab7449ad 0.600000000000 1835250 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": 1347343, "vin": [ { "gen": { "height": 1347333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99eae5ed5fd8ed9734c20defb2994bf6d29cbae26a1eb71bfc16c27fab7449ad" } } ], "extra": [ 1, 101, 229, 33, 208, 166, 100, 26, 188, 9, 135, 250, 62, 240, 96, 46, 73, 238, 135, 83, 163, 194, 32, 250, 81, 82, 122, 28, 226, 173, 35, 116, 162, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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