← previous blocknext block →recent activity
Analyzing
Block #96,614,324
6 transactions · 6 stateful · 2026-08-16 22:54:55 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,614,324 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x73dfcba5…1873
0x34b655…2a6f
4 touches
1 conflict
0x02c7fac9…a15f
0x34b655…2a6f
2 touches
0 conflicts
0x1907196e…8745
0x34b655…2a6f
2 touches
0 conflicts
0x37bef14c…a6d5
0x34b655…2a6f
2 touches
0 conflicts
0x3cbfa5aa…cc9b
0x34b655…2a6f
2 touches
0 conflicts
0x3ff58865…cdd3
0x34b655…2a6f
2 touches
0 conflicts
0x4450265f…f50d
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity