Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb0d0c03465ea0cf5f26d6b115d988f1500edf58d1e4fae0bf633516baa2a30

Tx prefix hash: 441594967d2d137948412ab6ea81cc08361e2db4c2d8f718bda7fb752e993278
Tx public key: 540dbefeb42974ebf6223ee75ea35dccc0c5c30dc4789e15b947324b38d02b27
Timestamp: 1771412272 Timestamp [UTC]: 2026-02-18 10:57:52 Age [y:d:h:m:s]: 00:272:11:17:20
Block: 1480429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200252 RingCT/type: yes/0
Extra: 01540dbefeb42974ebf6223ee75ea35dccc0c5c30dc4789e15b947324b38d02b27021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2059ca8c5b64ea4f5daa8c98b5a6b09c75dfc0a2bbeb1268fdc76e84c07931a 0.000600000000 1969797 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": 1480439, "vin": [ { "gen": { "height": 1480429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2059ca8c5b64ea4f5daa8c98b5a6b09c75dfc0a2bbeb1268fdc76e84c07931a" } } ], "extra": [ 1, 84, 13, 190, 254, 180, 41, 116, 235, 246, 34, 62, 231, 94, 163, 93, 204, 192, 197, 195, 13, 196, 120, 158, 21, 185, 71, 50, 75, 56, 208, 43, 39, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: