← previous blocknext block →recent activity
Analyzing
Block #96,146,216
7 transactions · 6 stateful · 2026-08-15 07:40:14 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,146,216 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0xe3c082c7…f032
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x011b5f0b…44d0
0x34b655…2a6f
2 touches
0 conflicts
0x0eb3ab36…88b9
0x34b655…2a6f
2 touches
0 conflicts
0x0eb3ab36…88ba
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x16f8e14a…f6e4
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 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity