Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47aefb9d3d3a811082cf05c7fbfae6e3a577c4132f450b64945d9a27e63ecee9

Tx prefix hash: 58719c9e5ed7ae45743dc24a618d1462e10121d0e66de63f25a7cfd07a69fa82
Tx public key: 4b822bb1d92037eeb0415e8aebd99654f8c573eb17540fca3b7d694c8a16bd4b
Timestamp: 1742344683 Timestamp [UTC]: 2025-03-19 00:38:03 Age [y:d:h:m:s]: 01:054:08:25:36
Block: 1242351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289640 RingCT/type: yes/0
Extra: 014b822bb1d92037eeb0415e8aebd99654f8c573eb17540fca3b7d694c8a16bd4b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b4415b7cf9babeab0ace09a80add697b566056384030df2c21304bfc08c061d 0.000600000000 1729324 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": 1242361, "vin": [ { "gen": { "height": 1242351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4415b7cf9babeab0ace09a80add697b566056384030df2c21304bfc08c061d" } } ], "extra": [ 1, 75, 130, 43, 177, 217, 32, 55, 238, 176, 65, 94, 138, 235, 217, 150, 84, 248, 197, 115, 235, 23, 84, 15, 202, 59, 125, 105, 76, 138, 22, 189, 75, 2, 17, 0, 0, 0, 3, 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: