Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0bce7f5e4a7c815e4d762936e3fbd8c139838c90cd20edfbf2498227cd78dcb

Tx prefix hash: 1ba3b1fa0098fdf6d71a4fd99e3174c0a58dc443f48e43ad97838aa7455d8861
Tx public key: cdec2c4fda759d730be65d3a5ee62770c320a8798cf8e530ca4864edb8a3d9d7
Timestamp: 1787816362 Timestamp [UTC]: 2026-08-27 07:39:22 Age [y:d:h:m:s]: 00:082:14:53:23
Block: 1622002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 58688 RingCT/type: yes/0
Extra: 01cdec2c4fda759d730be65d3a5ee62770c320a8798cf8e530ca4864edb8a3d9d7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f1787ea7e12727b2f6ea12c1b1632d78539c63c6f92227b46bb3d5f3f9b3fa1b 0.000600000000 2112022 of 15 <81>

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": 1622012, "vin": [ { "gen": { "height": 1622002 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f1787ea7e12727b2f6ea12c1b1632d78539c63c6f92227b46bb3d5f3f9b3fa1b", "view_tag": "81" } } } ], "extra": [ 1, 205, 236, 44, 79, 218, 117, 157, 115, 11, 230, 93, 58, 94, 230, 39, 112, 195, 32, 168, 121, 140, 248, 229, 48, 202, 72, 100, 237, 184, 163, 217, 215 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: