Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fe3581a307e0f99b2a02ae92961b8f2785eed2030b9f1bc0ea413e150c16639

Tx prefix hash: 43e5197ab46bbd83778a4d77546d1d8dcb6a4259701f58f87349025f5346da28
Tx public key: a1a6e6b4f371b0c552107ba0a8054306a95de8b494dbc282330280e001d5c8f8
Timestamp: 1765793669 Timestamp [UTC]: 2025-12-15 10:14:29 Age [y:d:h:m:s]: 00:147:07:34:36
Block: 1434071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97458 RingCT/type: yes/0
Extra: 01a1a6e6b4f371b0c552107ba0a8054306a95de8b494dbc282330280e001d5c8f802110000000270609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4ab50a80e28c121cb23b780889c6a2e5ed4a49e5b2ceb2d8c6cfeb26b7dd8e29 0.000600000000 1922852 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": 1434081, "vin": [ { "gen": { "height": 1434071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ab50a80e28c121cb23b780889c6a2e5ed4a49e5b2ceb2d8c6cfeb26b7dd8e29" } } ], "extra": [ 1, 161, 166, 230, 180, 243, 113, 176, 197, 82, 16, 123, 160, 168, 5, 67, 6, 169, 93, 232, 180, 148, 219, 194, 130, 51, 2, 128, 224, 1, 213, 200, 248, 2, 17, 0, 0, 0, 2, 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: