Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00566e20942d3c73bafb13a0c7d22b1fcfb736f33c2201dfb1726d9bf2a1c5e2

Tx prefix hash: a5c3799fd329431e23b215863e08980197b19d7e4a7fbb3a8dd37d853c9bb645
Tx public key: 25e2c95f3f84c8ee33c6eb044874c9dabe65b7f5a69d204e54d38b1fb8e66b12
Timestamp: 1774779371 Timestamp [UTC]: 2026-03-29 10:16:11 Age [y:d:h:m:s]: 00:230:03:56:48
Block: 1508297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 169890 RingCT/type: yes/0
Extra: 0125e2c95f3f84c8ee33c6eb044874c9dabe65b7f5a69d204e54d38b1fb8e66b12

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1f1dcb2d2ea08f9cb34fdc23d320d5ba4ae62eefab77e1f0b872435231353659 0.000600000000 1998049 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": 1508307, "vin": [ { "gen": { "height": 1508297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f1dcb2d2ea08f9cb34fdc23d320d5ba4ae62eefab77e1f0b872435231353659" } } ], "extra": [ 1, 37, 226, 201, 95, 63, 132, 200, 238, 51, 198, 235, 4, 72, 116, 201, 218, 190, 101, 183, 245, 166, 157, 32, 78, 84, 211, 139, 31, 184, 230, 107, 18 ], "rct_signatures": { "type": 0 } }


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