Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655200b0f8e58ce642e08bc4f181db489564358f8ceb59b36582cfdc1d8ba9bb

Tx prefix hash: cd57cc2a74b1affe4bb1040c188e50eabc077a37116e286d178666b2f8d18387
Tx public key: 570e411d45dbe97c882f72e41a57aec0c3cc74539b544c3573d2fb88e964c9ba
Timestamp: 1642681652 Timestamp [UTC]: 2022-01-20 12:27:32 Age [y:d:h:m:s]: 04:303:06:36:17
Block: 421361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1259968 RingCT/type: yes/0
Extra: 01570e411d45dbe97c882f72e41a57aec0c3cc74539b544c3573d2fb88e964c9ba021100000024e778ec4c000000000000000000

1 output(s) for total of 0.024652241438 xmr

stealth address amount amount idx tag
00: e331107a447c67a1b89325a154d67aa5eaec6947681071d9e1d25eb6bf64b9b6 0.024652241438 828914 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": 421371, "vin": [ { "gen": { "height": 421361 } } ], "vout": [ { "amount": 24652241438, "target": { "key": "e331107a447c67a1b89325a154d67aa5eaec6947681071d9e1d25eb6bf64b9b6" } } ], "extra": [ 1, 87, 14, 65, 29, 69, 219, 233, 124, 136, 47, 114, 228, 26, 87, 174, 192, 195, 204, 116, 83, 155, 84, 76, 53, 115, 210, 251, 136, 233, 100, 201, 186, 2, 17, 0, 0, 0, 36, 231, 120, 236, 76, 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: