Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2cc923ea9a28e5792402e5ee30b0f45b60314a2ba9097da2f74e035906c6f4e

Tx prefix hash: d64aa476b5bad42340fa1f9681eb930e553d7f463d6285bddbb1559e89a404fd
Tx public key: 8f5732af170b147e5ab6533314724992e5724fcee9c49ffcd38eff4659007a1d
Timestamp: 1728583506 Timestamp [UTC]: 2024-10-10 18:05:06 Age [y:d:h:m:s]: 02:034:21:39:40
Block: 1128714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549526 RingCT/type: yes/0
Extra: 018f5732af170b147e5ab6533314724992e5724fcee9c49ffcd38eff4659007a1d02110000000291e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c324bc8fd3bd0c39540d4fdb90d8729cca8ea4ae438eccbbc172e0d87f2eb0a7 0.000600000000 1611535 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": 1128724, "vin": [ { "gen": { "height": 1128714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c324bc8fd3bd0c39540d4fdb90d8729cca8ea4ae438eccbbc172e0d87f2eb0a7" } } ], "extra": [ 1, 143, 87, 50, 175, 23, 11, 20, 126, 90, 182, 83, 51, 20, 114, 73, 146, 229, 114, 79, 206, 233, 196, 159, 252, 211, 142, 255, 70, 89, 0, 122, 29, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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: