← previous blocknext block →recent activity
Analyzing
Block #96,291,581
7 transactions · 5 stateful · 2026-08-15 19:51:21 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,291,581 · 7 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
2w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c49ba5c…742e
0x34b655…2a6f
4 touches
1 conflict
0x5a0a2b03…ac50
0x34b655…2a6f
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0x0a0d9257…eef6
0x34b655…2a6f
2 touches
0 conflicts
0x166e9860…6947
0x34b655…2a6f
2 touches
0 conflicts
0x2a431ace…5f07
0x34b655…2a6f
2 touches
0 conflicts
0x2b93819b…32c3
0x34b655…2a6f
2 touches
0 conflicts
0x665ed7c9…f337
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 0x4c49ba5c83…19742e
Audit this contract →
← previous block·next block →recent activity