← previous blocknext block →recent activity
Analyzing
Block #96,026,628
13 transactions · 12 stateful · 2026-08-14 21:38:40 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,026,628 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w27w38w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5085ca5…c9b0
0x34b655…2a6f
12 touches
15 conflicts
0xfaa5c672…5681
0x34b655…2a6f
4 touches
1 conflict
0x748ce49f…a12c
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e6e219f…f3a0
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd95f6529…af73
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xf5085ca50b…5ac9b0
Audit this contract →
← previous block·next block →recent activity