Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a5504ee8bf96dbdb207bba339e6e0559e7dec8c5f031a45fdcd694d0c9561b

Tx prefix hash: d7cb82cf0a955612d2b6c285824b34d9532aff1cf129e3521ca1e33af753fd5d
Tx public key: 72945cfd824f5f48d4cfd5d315c1582b6fe8f9ea7fcdedc0969079ec4db6d054
Timestamp: 1705605373 Timestamp [UTC]: 2024-01-18 19:16:13 Age [y:d:h:m:s]: 02:305:11:22:44
Block: 938200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 743499 RingCT/type: yes/0
Extra: 0172945cfd824f5f48d4cfd5d315c1582b6fe8f9ea7fcdedc0969079ec4db6d0540211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 22640e736978240e225a2c2f4ea4fc55219225d512d7e0c8d5ad6303b45d7d98 0.000600000000 1396270 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": 938210, "vin": [ { "gen": { "height": 938200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22640e736978240e225a2c2f4ea4fc55219225d512d7e0c8d5ad6303b45d7d98" } } ], "extra": [ 1, 114, 148, 92, 253, 130, 79, 95, 72, 212, 207, 213, 211, 21, 193, 88, 43, 111, 232, 249, 234, 127, 205, 237, 192, 150, 144, 121, 236, 77, 182, 208, 84, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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: