Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53ec35adaa04c94e66b61b8bb8ccf86987bf7ccc57a2fca8183ae0b86d3a9773

Tx prefix hash: 51d449a7221df4c59ba582e07563311394008a5b389e7edfc3eec4d1fa90a579
Tx public key: 275c72fa05f5e5c6f1fffb3d414e301a9a175e3d4d379887c4d5d4359a829ea8
Timestamp: 1791977766 Timestamp [UTC]: 2026-10-14 11:36:06 Age [y:d:h:m:s]: 00:030:09:56:17
Block: 1654255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 23417 RingCT/type: yes/0
Extra: 01275c72fa05f5e5c6f1fffb3d414e301a9a175e3d4d379887c4d5d4359a829ea8

1 output(s) for total of 0.000602803840 xmr

stealth address amount amount idx tag
00: 7a0a57056ea5df5f5fe98b00532e68e4b363c46d0dc56e3ddec2eff0a1110d9c 0.000602803840 2144563 of 0 <1d>

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": 1654265, "vin": [ { "gen": { "height": 1654255 } } ], "vout": [ { "amount": 602803840, "target": { "tagged_key": { "key": "7a0a57056ea5df5f5fe98b00532e68e4b363c46d0dc56e3ddec2eff0a1110d9c", "view_tag": "1d" } } } ], "extra": [ 1, 39, 92, 114, 250, 5, 245, 229, 198, 241, 255, 251, 61, 65, 78, 48, 26, 154, 23, 94, 61, 77, 55, 152, 135, 196, 213, 212, 53, 154, 130, 158, 168 ], "rct_signatures": { "type": 0 } }


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