← previous blocknext block →recent activity
Analyzing
Block #96,827,843
10 transactions · 10 stateful · 2026-08-17 16:48:50 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,827,843 · 10 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
1w02w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe6623bec…4b20
0x34b655…2a6f
3 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
2 touches
0 conflicts
0x463e8557…882c
0x34b655…2a6f
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 0x2b64d0d7f5…78af06
Audit this contract →
← previous block·next block →recent activity