Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e13372bcd4b4af4597ece1cb49d9b5b54d822d176aedb8f77e22f96b1e9b3fd

Tx prefix hash: 349eeb61b880ddd3ea50ce5bc606d7e15f535336bc82bea7446ca5c96aace68b
Tx public key: d4787318ffb2e2a28e3e0c7e43d95ca15ae5e5eac8ce461af556a4f72ae19789
Timestamp: 1781229890 Timestamp [UTC]: 2026-06-12 02:04:50 Age [y:d:h:m:s]: 00:161:14:40:10
Block: 1557146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 125686 RingCT/type: yes/0
Extra: 01d4787318ffb2e2a28e3e0c7e43d95ca15ae5e5eac8ce461af556a4f72ae19789

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc52d1f44734adae0e32e476bf3b4f0a7377b66ebf1c00e5f103e538c4e8c7ec 0.000600000000 2047124 of 15 <9b>

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": 1557156, "vin": [ { "gen": { "height": 1557146 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "cc52d1f44734adae0e32e476bf3b4f0a7377b66ebf1c00e5f103e538c4e8c7ec", "view_tag": "9b" } } } ], "extra": [ 1, 212, 120, 115, 24, 255, 178, 226, 162, 142, 62, 12, 126, 67, 217, 92, 161, 90, 229, 229, 234, 200, 206, 70, 26, 245, 86, 164, 247, 42, 225, 151, 137 ], "rct_signatures": { "type": 0 } }


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