← previous blocknext block →recent activity
Analyzing
Block #95,390,802
17 transactions · 16 stateful · 2026-08-12 16:18:08 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,390,802 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc972e681…a180
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x26d8622c…e8af
0x34b655…2a6f
3 touches
1 conflict
0xe2263bea…6a9d
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa0
0x2b46c0…1669
2 touches
0 conflicts
0xeba56708…8cd7
0x2b46c0…1669
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xc972e6811f…dca180
Audit this contract →
← previous block·next block →recent activity