Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c45a2003bbe545db44b2a74b3530606ac7ed22f6877687b183d2a8479ddc4348

Tx prefix hash: d739b8ecdf4963f4d6301bd86dc6a541377802663d9bd2eff0df77bf1e515c4d
Tx public key: 01748b5d90f3a6ad9de47d0428f5b113094a3d8718e0bb1fb09846b557763d6f
Timestamp: 1773213429 Timestamp [UTC]: 2026-03-11 07:17:09 Age [y:d:h:m:s]: 00:251:07:44:19
Block: 1495337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185119 RingCT/type: yes/0
Extra: 0101748b5d90f3a6ad9de47d0428f5b113094a3d8718e0bb1fb09846b557763d6f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b12841847949c22db9b620b0e3f02b67ef0ad12ac5e340ea2aa69bef2b21c0d 0.000600000000 1984947 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": 1495347, "vin": [ { "gen": { "height": 1495337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b12841847949c22db9b620b0e3f02b67ef0ad12ac5e340ea2aa69bef2b21c0d" } } ], "extra": [ 1, 1, 116, 139, 93, 144, 243, 166, 173, 157, 228, 125, 4, 40, 245, 177, 19, 9, 74, 61, 135, 24, 224, 187, 31, 176, 152, 70, 181, 87, 118, 61, 111, 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: