Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61daaa8c2f0338b0b2d3e2dc57dc1ed0e44720d96fb9aa611df147e027c0f46b

Tx prefix hash: a07f331a7e9a39f3f61b9a4448c8edd48eebbbc5a94beebc6ea9aba252ebcfa2
Tx public key: bc72f4d425794ae09b4b3f52d4cba2985c1a3dd9a1225661d5adf9cab41ed907
Timestamp: 1791190294 Timestamp [UTC]: 2026-10-05 08:51:34 Age [y:d:h:m:s]: 00:039:17:50:57
Block: 1648627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 29198 RingCT/type: yes/0
Extra: 01bc72f4d425794ae09b4b3f52d4cba2985c1a3dd9a1225661d5adf9cab41ed907

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd158b13445008ac853a83332890e2a8b1eb8b1040aa7be05b1ad27244c0ef78 0.000600000000 2138783 of 15 <c9>

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": 1648637, "vin": [ { "gen": { "height": 1648627 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "cd158b13445008ac853a83332890e2a8b1eb8b1040aa7be05b1ad27244c0ef78", "view_tag": "c9" } } } ], "extra": [ 1, 188, 114, 244, 212, 37, 121, 74, 224, 155, 75, 63, 82, 212, 203, 162, 152, 92, 26, 61, 217, 161, 34, 86, 97, 213, 173, 249, 202, 180, 30, 217, 7 ], "rct_signatures": { "type": 0 } }


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