Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5963d5f651faf948afa614d4c0477edfb4c3ca30aa9ed1e4b11c0a4b453acf0e

Tx prefix hash: 974df93b40b55c79e07547aca44ba8377aaa434247cd52c6160da62d42943e18
Tx public key: 2e9c50a09404cd0a60fdb4d64799fbe78028ff4f6b8bbad8d37ddae9c0a529c3
Timestamp: 1755365948 Timestamp [UTC]: 2025-08-16 17:39:08 Age [y:d:h:m:s]: 01:094:14:40:19
Block: 1347966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333785 RingCT/type: yes/0
Extra: 012e9c50a09404cd0a60fdb4d64799fbe78028ff4f6b8bbad8d37ddae9c0a529c3021100000003a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6a38f100da70b5a8c546b0b0e7de0c1d1b989e0c2e03deae33c048ac495a7f9 0.000600000000 1835889 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": 1347976, "vin": [ { "gen": { "height": 1347966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a38f100da70b5a8c546b0b0e7de0c1d1b989e0c2e03deae33c048ac495a7f9" } } ], "extra": [ 1, 46, 156, 80, 160, 148, 4, 205, 10, 96, 253, 180, 214, 71, 153, 251, 231, 128, 40, 255, 79, 107, 139, 186, 216, 211, 125, 218, 233, 192, 165, 41, 195, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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: