Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05197cccbf5ff00eef74b28ea78b8e78e5f696d63b44ee72d1c777f8bb126b94

Tx prefix hash: 67d82e0dabc78727b424a617925b49776d8663f2e727b0b71022238ffe65a151
Tx public key: 037196d9f6517c0efa34e5391080e7e149d7e2d53b345ffd327e32eb15c7f296
Timestamp: 1766466084 Timestamp [UTC]: 2025-12-23 05:01:24 Age [y:d:h:m:s]: 00:326:23:16:20
Block: 1439641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238993 RingCT/type: yes/0
Extra: 01037196d9f6517c0efa34e5391080e7e149d7e2d53b345ffd327e32eb15c7f296021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d5932522c032290d974fabf5452ba08e758422965f7f1668139e9d8ce12fa59d 0.000600000000 1928488 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": 1439651, "vin": [ { "gen": { "height": 1439641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5932522c032290d974fabf5452ba08e758422965f7f1668139e9d8ce12fa59d" } } ], "extra": [ 1, 3, 113, 150, 217, 246, 81, 124, 14, 250, 52, 229, 57, 16, 128, 231, 225, 73, 215, 226, 213, 59, 52, 95, 253, 50, 126, 50, 235, 21, 199, 242, 150, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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: