Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db509b4d6787fe87ba010269b6b41e73e950c46738bf748c2a49eebcaaf2aa6f

Tx prefix hash: 51af544e874d1a83cd576da565d48eb79f9bcf74a694ceeff0ce05b308093ed7
Tx public key: bbb09679911104a2c9c05cb2deab6a59f406408da82cd64f626db171192a21e9
Timestamp: 1759147638 Timestamp [UTC]: 2025-09-29 12:07:18 Age [y:d:h:m:s]: 01:050:08:22:31
Block: 1378994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302377 RingCT/type: yes/0
Extra: 01bbb09679911104a2c9c05cb2deab6a59f406408da82cd64f626db171192a21e902110000000397baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d98435fd915a859697d2235dfbf600921c5ef55f1c5c3d4ab209b11d5570f8e4 0.000600000000 1867091 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": 1379004, "vin": [ { "gen": { "height": 1378994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98435fd915a859697d2235dfbf600921c5ef55f1c5c3d4ab209b11d5570f8e4" } } ], "extra": [ 1, 187, 176, 150, 121, 145, 17, 4, 162, 201, 192, 92, 178, 222, 171, 106, 89, 244, 6, 64, 141, 168, 44, 214, 79, 98, 109, 177, 113, 25, 42, 33, 233, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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: