Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778e1e537ed3e28bd57057649f3d1b46cd8a7107c50ba83bfeeb60c115282f90

Tx prefix hash: a156a579376954f58a62b6adf9a0feccdeeb12595167cc02763d9937e2637069
Tx public key: ccb2ff6fcf6a2a58c98eaca6a41fee154198f21215fea7e15cfcf11518ace7a0
Timestamp: 1719054966 Timestamp [UTC]: 2024-06-22 11:16:06 Age [y:d:h:m:s]: 02:151:14:22:54
Block: 1049711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633372 RingCT/type: yes/0
Extra: 01ccb2ff6fcf6a2a58c98eaca6a41fee154198f21215fea7e15cfcf11518ace7a0021100000001d749f511000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d2352b13aeb8653de35d0e00ee56a3789704540d05ee67f1f69cc45a0c408542 0.000600000000 1519814 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": 1049721, "vin": [ { "gen": { "height": 1049711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2352b13aeb8653de35d0e00ee56a3789704540d05ee67f1f69cc45a0c408542" } } ], "extra": [ 1, 204, 178, 255, 111, 207, 106, 42, 88, 201, 142, 172, 166, 164, 31, 238, 21, 65, 152, 242, 18, 21, 254, 167, 225, 92, 252, 241, 21, 24, 172, 231, 160, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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: