Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5243be41d5c08aa4a5a835ab6472570ea418edc37ea4fb37c6fd024d819e67e6

Tx prefix hash: 77507479d423ee6a59e83b6e84b4841c600a4c40d1b3244b32033f9933ec676e
Tx public key: 0af4e6d3a1aed061558ca2d8a3eb3e668a301fa01377ced21ca1aed955f9c3c0
Timestamp: 1649611927 Timestamp [UTC]: 2022-04-10 17:32:07 Age [y:d:h:m:s]: 04:040:00:47:06
Block: 477408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1061028 RingCT/type: yes/0
Extra: 010af4e6d3a1aed061558ca2d8a3eb3e668a301fa01377ced21ca1aed955f9c3c0021100000001a8c141c5000000000000000000

1 output(s) for total of 0.016074939724 xmr

stealth address amount amount idx tag
00: c86d64d0cf54382047750f329abe3fac4ca0c8769bf23cbffc1c4dd5128d36b8 0.016074939724 898069 of 0 -

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": 477418, "vin": [ { "gen": { "height": 477408 } } ], "vout": [ { "amount": 16074939724, "target": { "key": "c86d64d0cf54382047750f329abe3fac4ca0c8769bf23cbffc1c4dd5128d36b8" } } ], "extra": [ 1, 10, 244, 230, 211, 161, 174, 208, 97, 85, 140, 162, 216, 163, 235, 62, 102, 138, 48, 31, 160, 19, 119, 206, 210, 28, 161, 174, 217, 85, 249, 195, 192, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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: