Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaa8693bc5bcc8c398eb0d801b7c0a2d70daccb6dce665b10f0d26a2883faa70

Tx prefix hash: 2a784f931df8bcb2f6dbcb19e1fbcbb8ce4ba3477184923b6279f660063e7413
Tx public key: 394fd8821e8fc71d4ddb84937e4b7c04d984e64106e154a9815d853e79b5b15d
Timestamp: 1750896400 Timestamp [UTC]: 2025-06-26 00:06:40 Age [y:d:h:m:s]: 01:143:13:22:43
Block: 1312812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366858 RingCT/type: yes/0
Extra: 01394fd8821e8fc71d4ddb84937e4b7c04d984e64106e154a9815d853e79b5b15d0211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80f5c67ecb71ed9e226ae867c3a851b1117df5ec7a22d3411f5f6f9c9e9d88c4 0.000600000000 1800447 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": 1312822, "vin": [ { "gen": { "height": 1312812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80f5c67ecb71ed9e226ae867c3a851b1117df5ec7a22d3411f5f6f9c9e9d88c4" } } ], "extra": [ 1, 57, 79, 216, 130, 30, 143, 199, 29, 77, 219, 132, 147, 126, 75, 124, 4, 217, 132, 230, 65, 6, 225, 84, 169, 129, 93, 133, 62, 121, 181, 177, 93, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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: