← previous blocknext block →recent activity
Analyzing
Block #95,750,879
13 transactions · 13 stateful · 2026-08-13 22:31:15 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,750,879 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w18w29w311w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
8 touches
6 conflicts
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x16778714…a6c9
0x34b655…2a6f
6 touches
3 conflicts
0x01b70050…6db2
0x34b655…2a6f
6 touches
3 conflicts
0x6b09fb8c…5518
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x8b76e9f2…54ee
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 0xc5a1b2febf…f05369
Audit this contract →
← previous block·next block →recent activity