Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aaf53e5e6d7483dfb18704a1c9c5a1183c5606e95dfad970fb0be38bca77c53

Tx prefix hash: af98dfbc8aec0ec560166cd16e91929ecd21d86991d6d5b179ef4016ae5ccaa0
Tx public key: 17238415a07ae029052c6ec4d30d15896b14a0e880520b35e5796122c74c775a
Timestamp: 1730084603 Timestamp [UTC]: 2024-10-28 03:03:23 Age [y:d:h:m:s]: 02:024:13:28:30
Block: 1141087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542407 RingCT/type: yes/0
Extra: 0117238415a07ae029052c6ec4d30d15896b14a0e880520b35e5796122c74c775a021100000005a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f6595c74dbb06aa23e108ebfd6a8b7f4393151d918e8fed3b49cc001624a4810 0.000600000000 1624894 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": 1141097, "vin": [ { "gen": { "height": 1141087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6595c74dbb06aa23e108ebfd6a8b7f4393151d918e8fed3b49cc001624a4810" } } ], "extra": [ 1, 23, 35, 132, 21, 160, 122, 224, 41, 5, 44, 110, 196, 211, 13, 21, 137, 107, 20, 160, 232, 128, 82, 11, 53, 229, 121, 97, 34, 199, 76, 119, 90, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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: