Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67ad643e78b8e2919cdc5d96ccffeb79820d9be16610e86c102ae3fa472f99ff

Tx prefix hash: cb74d59f4a6bf2d2a6631dc10b3e4c60c76193ea8f85bb5f813289560b67ff6b
Tx public key: 025f5a93a8b031f89f8f7e316183741e732f983d6366e65819d9fc5aa7fa4248
Timestamp: 1771939348 Timestamp [UTC]: 2026-02-24 13:22:28 Age [y:d:h:m:s]: 00:268:12:57:19
Block: 1484812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197515 RingCT/type: yes/0
Extra: 01025f5a93a8b031f89f8f7e316183741e732f983d6366e65819d9fc5aa7fa4248021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b120d202981942db38fd36d9df9cdaaf2b211acbe0f4d941e22348e0be266fe2 0.000600000000 1974242 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": 1484822, "vin": [ { "gen": { "height": 1484812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b120d202981942db38fd36d9df9cdaaf2b211acbe0f4d941e22348e0be266fe2" } } ], "extra": [ 1, 2, 95, 90, 147, 168, 176, 49, 248, 159, 143, 126, 49, 97, 131, 116, 30, 115, 47, 152, 61, 99, 102, 230, 88, 25, 217, 252, 90, 167, 250, 66, 72, 2, 17, 0, 0, 0, 3, 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: