← previous blocknext block →recent activity
Analyzing
Block #96,116,294
12 transactions · 11 stateful · 2026-08-15 05:09:40 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,116,294 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w07w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c1a0106…de12
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x32790195…b240
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x998a1167…81f9
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
6 conflicts on slot 0x9c1a01065d…9fde12
Audit this contract →
← previous block·next block →recent activity