Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c0bc3bc2488a046df4a4d61a78b5d309367c4a73483efd186033ab04be5e7cf

Tx prefix hash: e5be9e8c5a1d16ea4817a7e582f93593a20b84be6d8a44f56d71473da48bf1a2
Tx public key: 1b70cd47b3c57be8cf4c10b1465b4c370914250da91f48c054d6df2e28e3e807
Timestamp: 1790220600 Timestamp [UTC]: 2026-09-24 03:30:00 Age [y:d:h:m:s]: 00:053:10:33:09
Block: 1642266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 37422 RingCT/type: yes/0
Extra: 011b70cd47b3c57be8cf4c10b1465b4c370914250da91f48c054d6df2e28e3e807

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d862f307ebfdef7555841d415f0bc761ca8e4dea1e716f2ca8585bc2884b8a92 0.000600000000 2132310 of 15 <2e>

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": 1642276, "vin": [ { "gen": { "height": 1642266 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d862f307ebfdef7555841d415f0bc761ca8e4dea1e716f2ca8585bc2884b8a92", "view_tag": "2e" } } } ], "extra": [ 1, 27, 112, 205, 71, 179, 197, 123, 232, 207, 76, 16, 177, 70, 91, 76, 55, 9, 20, 37, 13, 169, 31, 72, 192, 84, 214, 223, 46, 40, 227, 232, 7 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: