← previous blocknext block →recent activity
Analyzing
Block #93,075,115
12 transactions · 12 stateful · 2026-08-04 13:40:31 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,075,115 · 12 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
1w02w03w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8435cea0…f5b6
0x34b655…2a6f
4 touches
1 conflict
0xa3dc5db6…1c01
0x34b655…2a6f
4 touches
1 conflict
0xdf4da882…1619
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x0419260c…d008
0x34b655…2a6f
2 touches
0 conflicts
0x0419260c…d009
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
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 0x8435cea01a…60f5b6
Audit this contract →
← previous block·next block →recent activity