Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1bc9ce894b13ef8b62ab96b794e442378deccbf3e8a5fcf909142c6a7ebb4d

Tx prefix hash: 8d9c6fc9acb374844902338e65d9527b3031863b5d90cf64e781e6397b8a801b
Tx public key: d9ab46ac1c3e4465a2f9fd0c4d16a9299f7fbeb91ef35e7244d73e418d197072
Timestamp: 1774738128 Timestamp [UTC]: 2026-03-28 22:48:48 Age [y:d:h:m:s]: 00:234:14:27:15
Block: 1507952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173198 RingCT/type: yes/0
Extra: 01d9ab46ac1c3e4465a2f9fd0c4d16a9299f7fbeb91ef35e7244d73e418d197072021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc37878e4235e5dbd5ca9ebfb2f8d70143afc4f66546de29cd1750d3dbd48b09 0.000600000000 1997704 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": 1507962, "vin": [ { "gen": { "height": 1507952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc37878e4235e5dbd5ca9ebfb2f8d70143afc4f66546de29cd1750d3dbd48b09" } } ], "extra": [ 1, 217, 171, 70, 172, 28, 62, 68, 101, 162, 249, 253, 12, 77, 22, 169, 41, 159, 127, 190, 185, 30, 243, 94, 114, 68, 215, 62, 65, 141, 25, 112, 114, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: