← previous blocknext block →recent activity
Analyzing
Block #96,179,365
10 transactions · 7 stateful · 2026-08-15 10:26:57 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,179,365 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x96efe05d…5d48
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x0bd5255a…a83a
0x34b655…2a6f
2 touches
0 conflicts
0x18c27ce0…4b1d
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c70
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
3 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity