Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d5776f3b5d3d6244007b59e2ef1241398dac734a8d9fe2e7d4ee2d78902ae0

Tx prefix hash: eebeab407dda1642ca6737c4959c9706043683caf46cbadd12e0337b6d6e25cf
Tx public key: 2d89dce731d7957ca0136a8688671a9a3edd975adfcf34c7d54eac6b302e4ff2
Timestamp: 1743509255 Timestamp [UTC]: 2025-04-01 12:07:35 Age [y:d:h:m:s]: 01:227:23:09:48
Block: 1251957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426897 RingCT/type: yes/0
Extra: 012d89dce731d7957ca0136a8688671a9a3edd975adfcf34c7d54eac6b302e4ff2021100000009a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 51402ecea43990e5a10005ac262172db3da10216d78151c4789d119e3b368d0f 0.000600000000 1739034 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": 1251967, "vin": [ { "gen": { "height": 1251957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51402ecea43990e5a10005ac262172db3da10216d78151c4789d119e3b368d0f" } } ], "extra": [ 1, 45, 137, 220, 231, 49, 215, 149, 124, 160, 19, 106, 134, 136, 103, 26, 154, 62, 221, 151, 90, 223, 207, 52, 199, 213, 78, 172, 107, 48, 46, 79, 242, 2, 17, 0, 0, 0, 9, 162, 237, 1, 107, 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: