Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae4a2ecc0ae4e544ef4a79d1027df9da788f121e7997765f416dcaa1314ac0b

Tx prefix hash: d330b69b24e398d421c8f4c39ec192048dfed09e25528d0a52eec93cf5cc3afc
Tx public key: 6af7cec80ad7c9f3e3d4a21604888129b9110be4ed182cfd71a2a43a92c71fb6
Timestamp: 1742089756 Timestamp [UTC]: 2025-03-16 01:49:16 Age [y:d:h:m:s]: 01:245:21:12:31
Block: 1240238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439744 RingCT/type: yes/0
Extra: 016af7cec80ad7c9f3e3d4a21604888129b9110be4ed182cfd71a2a43a92c71fb60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: caaceb1f2d1f7cf23714eb7dc62861e697182903804addfab1fc1ecdc63a12bc 0.000600000000 1727203 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": 1240248, "vin": [ { "gen": { "height": 1240238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caaceb1f2d1f7cf23714eb7dc62861e697182903804addfab1fc1ecdc63a12bc" } } ], "extra": [ 1, 106, 247, 206, 200, 10, 215, 201, 243, 227, 212, 162, 22, 4, 136, 129, 41, 185, 17, 11, 228, 237, 24, 44, 253, 113, 162, 164, 58, 146, 199, 31, 182, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: