Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc0f036ca89546becc0662f03c58b84beb5b1a99ac356bf70d5024e3de8157e

Tx prefix hash: 9ef1df8d1849c2e9334965bd36d921cd19e743cb275a653d3621cd39541850f2
Tx public key: 59cd25777663703f7297ed334f2e0b14c9133c51b9d5bdf7f8d354e0874c4772
Timestamp: 1636984286 Timestamp [UTC]: 2021-11-15 13:51:26 Age [y:d:h:m:s]: 05:008:06:34:02
Block: 374855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1309295 RingCT/type: yes/0
Extra: 0159cd25777663703f7297ed334f2e0b14c9133c51b9d5bdf7f8d354e0874c4772021100000006a272b9cb000000000000000000

1 output(s) for total of 0.035154779947 xmr

stealth address amount amount idx tag
00: c948e4c57e6819aa789eb5445e1cb5c46b44dc27eb35d52f0b03132f2bcb9f7e 0.035154779947 758643 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": 374865, "vin": [ { "gen": { "height": 374855 } } ], "vout": [ { "amount": 35154779947, "target": { "key": "c948e4c57e6819aa789eb5445e1cb5c46b44dc27eb35d52f0b03132f2bcb9f7e" } } ], "extra": [ 1, 89, 205, 37, 119, 118, 99, 112, 63, 114, 151, 237, 51, 79, 46, 11, 20, 201, 19, 60, 81, 185, 213, 189, 247, 248, 211, 84, 224, 135, 76, 71, 114, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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: