Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1583a5f098ccd9a5a684bd07a07fe11a4e5165b06551ec1678a52de9d2ec3f

Tx prefix hash: 938fa10ee6f281c0e75b8c4dc4ebb303353d6bda09fe23e57a70b0a9dc9b8de0
Tx public key: 3462a4b96d8518fd903147d4b3e5b289949be154b15c4fc2c41b1709ebe9dc88
Timestamp: 1764856476 Timestamp [UTC]: 2025-12-04 13:54:36 Age [y:d:h:m:s]: 00:345:11:12:45
Block: 1426323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252201 RingCT/type: yes/0
Extra: 013462a4b96d8518fd903147d4b3e5b289949be154b15c4fc2c41b1709ebe9dc8802110000000470609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e1e151863c1913e854b1450a34e5db1b8cbe3c958fef90fa55030dd93eafe0c 0.000600000000 1915014 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": 1426333, "vin": [ { "gen": { "height": 1426323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1e151863c1913e854b1450a34e5db1b8cbe3c958fef90fa55030dd93eafe0c" } } ], "extra": [ 1, 52, 98, 164, 185, 109, 133, 24, 253, 144, 49, 71, 212, 179, 229, 178, 137, 148, 155, 225, 84, 177, 92, 79, 194, 196, 27, 23, 9, 235, 233, 220, 136, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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: