Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee9926e5f9c0b5b240e9aac9fe1aec9985432aefb1c49ffbbf75f124fb3669b2

Tx prefix hash: b332640e89ec4d122b9e1cdbd26d4e559b1c8e5827ae7d19a2bceef68f8e6b6d
Tx public key: 0235a963864910e1a43ae63dcb0ed5d8e55a3816439406a872247a20a2804bf8
Timestamp: 1774371931 Timestamp [UTC]: 2026-03-24 17:05:31 Age [y:d:h:m:s]: 00:241:22:12:54
Block: 1504911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178579 RingCT/type: yes/0
Extra: 010235a963864910e1a43ae63dcb0ed5d8e55a3816439406a872247a20a2804bf8021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d245d5a42435d08b3f8e10f571128401fc3555cf627ee5db56389a4358a4e896 0.000600000000 1994639 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": 1504921, "vin": [ { "gen": { "height": 1504911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d245d5a42435d08b3f8e10f571128401fc3555cf627ee5db56389a4358a4e896" } } ], "extra": [ 1, 2, 53, 169, 99, 134, 73, 16, 225, 164, 58, 230, 61, 203, 14, 213, 216, 229, 90, 56, 22, 67, 148, 6, 168, 114, 36, 122, 32, 162, 128, 75, 248, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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