Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3bae5d2c20b4871ea34fcbf3dfd71dcdec629798ab05c889a24bbba907af3de

Tx prefix hash: e580820b4a048fe1ef07c53211ada7eed15a7a118fcdec57750ba4c953b331a9
Tx public key: 339d71b7f95015232abfad883b39907da8b7e9d1fa1a1d1dec02a200a94cba45
Timestamp: 1761041256 Timestamp [UTC]: 2025-10-21 10:07:36 Age [y:d:h:m:s]: 01:024:22:31:02
Block: 1394701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284074 RingCT/type: yes/0
Extra: 01339d71b7f95015232abfad883b39907da8b7e9d1fa1a1d1dec02a200a94cba45021100000002df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd001bd623880f5e2ebe7b79a7c88e51763a00874975cfdb128536b898b0c678 0.000600000000 1882976 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": 1394711, "vin": [ { "gen": { "height": 1394701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd001bd623880f5e2ebe7b79a7c88e51763a00874975cfdb128536b898b0c678" } } ], "extra": [ 1, 51, 157, 113, 183, 249, 80, 21, 35, 42, 191, 173, 136, 59, 57, 144, 125, 168, 183, 233, 209, 250, 26, 29, 29, 236, 2, 162, 0, 169, 76, 186, 69, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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: