Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b0ecf077043ebe94a6b386074ed85bca43cff365a3214ced2428dd3dceddc3

Tx prefix hash: c636ecbde3e5d28fa1b5072a1d5c01f1773a5a7ac35658f4950c21f282798b35
Tx public key: bc0090ded09c0c526266f5a84904932546f058b50e82b3582210d8dca7d6ac05
Timestamp: 1764028371 Timestamp [UTC]: 2025-11-24 23:52:51 Age [y:d:h:m:s]: 00:357:07:16:13
Block: 1419451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260767 RingCT/type: yes/0
Extra: 01bc0090ded09c0c526266f5a84904932546f058b50e82b3582210d8dca7d6ac05021100000003fb8fd089000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 33e1b16cda47f6206bb60896e401bd5600aba2c3ef1703442c9596d0e1314d2b 0.000600000000 1907988 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": 1419461, "vin": [ { "gen": { "height": 1419451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33e1b16cda47f6206bb60896e401bd5600aba2c3ef1703442c9596d0e1314d2b" } } ], "extra": [ 1, 188, 0, 144, 222, 208, 156, 12, 82, 98, 102, 245, 168, 73, 4, 147, 37, 70, 240, 88, 181, 14, 130, 179, 88, 34, 16, 216, 220, 167, 214, 172, 5, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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: