Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 263a2929d7e51889afec690724b4d31141a19625fa62c11c2851896e4fed6830

Tx prefix hash: 6865adf487bddf471c752a137888ba77f3e361e7c0d297728e034ddf37233738
Tx public key: f36be67bf6a1fa5fca15dcda360b805ac1e5f8d6ecd3d1c83e5debb8e9e0c229
Timestamp: 1742327345 Timestamp [UTC]: 2025-03-18 19:49:05 Age [y:d:h:m:s]: 01:247:01:33:41
Block: 1242204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440738 RingCT/type: yes/0
Extra: 01f36be67bf6a1fa5fca15dcda360b805ac1e5f8d6ecd3d1c83e5debb8e9e0c229021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97b1ea2e75e0c81247b910dcbbbda886bc0edbbccba7ed1c85599102ecb49598 0.000600000000 1729177 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": 1242214, "vin": [ { "gen": { "height": 1242204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97b1ea2e75e0c81247b910dcbbbda886bc0edbbccba7ed1c85599102ecb49598" } } ], "extra": [ 1, 243, 107, 230, 123, 246, 161, 250, 95, 202, 21, 220, 218, 54, 11, 128, 90, 193, 229, 248, 214, 236, 211, 209, 200, 62, 93, 235, 184, 233, 224, 194, 41, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: