Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b911e41c91d322b914175041663e5749b6fcaf4ad513963f62666f8796df667

Tx prefix hash: 5a93eb8440d84340fa0178143e29f50afa9c0ef3ed054a6a072a8efa908a585f
Tx public key: ed7aabf5bff8c87a234e98d7f827ec395507d56af2bf29f1da2f8dfa17466665
Timestamp: 1773748606 Timestamp [UTC]: 2026-03-17 11:56:46 Age [y:d:h:m:s]: 00:248:06:38:00
Block: 1499756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183107 RingCT/type: yes/0
Extra: 01ed7aabf5bff8c87a234e98d7f827ec395507d56af2bf29f1da2f8dfa17466665021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5c36e2ba376e3de28cc46213c540c1ce19384e0cd2c46bdc1238d46c0cab8d88 0.000600000000 1989420 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": 1499766, "vin": [ { "gen": { "height": 1499756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c36e2ba376e3de28cc46213c540c1ce19384e0cd2c46bdc1238d46c0cab8d88" } } ], "extra": [ 1, 237, 122, 171, 245, 191, 248, 200, 122, 35, 78, 152, 215, 248, 39, 236, 57, 85, 7, 213, 106, 242, 191, 41, 241, 218, 47, 141, 250, 23, 70, 102, 101, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: