Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 196b08718424ee0928ef2d668a5f8bdb0eaa1c375c7eb09fabf79ba94dcf4270

Tx prefix hash: 156f7f6a23d0cc37fd281cc7f91ced97a5daa058fa87c6fd60b525ade21fa116
Tx public key: dd162bcdf72d78ca2b8a4728ff1666f3314607783b906de16386edcdba6b14ea
Timestamp: 1771157384 Timestamp [UTC]: 2026-02-15 12:09:44 Age [y:d:h:m:s]: 00:274:08:56:17
Block: 1478322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201578 RingCT/type: yes/0
Extra: 01dd162bcdf72d78ca2b8a4728ff1666f3314607783b906de16386edcdba6b14ea021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de4f427550e9ebcb5376bfea5538c1b7418f1292424fd507924eb20a948cec48 0.000600000000 1967650 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 dinastycoin-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": 1478332, "vin": [ { "gen": { "height": 1478322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de4f427550e9ebcb5376bfea5538c1b7418f1292424fd507924eb20a948cec48" } } ], "extra": [ 1, 221, 22, 43, 205, 247, 45, 120, 202, 43, 138, 71, 40, 255, 22, 102, 243, 49, 70, 7, 120, 59, 144, 109, 225, 99, 134, 237, 205, 186, 107, 20, 234, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: