← previous blocknext block →recent activity
Analyzing
Block #93,445,899
11 transactions · 9 stateful · 2026-08-05 20:45:36 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,445,899 · 11 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
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf279bfea…5fd6
0x34b655…2a6f
4 touches
1 conflict
0x49bc9efc…8842
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1c43a9cd…6c4c
0x34b655…2a6f
2 touches
0 conflicts
0x1d2d55e0…ef26
0x34b655…2a6f
2 touches
0 conflicts
0x24ca1902…7a87
0x34b655…2a6f
2 touches
0 conflicts
0x518aa708…c018
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
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 0xf279bfea12…185fd6
Audit this contract →
← previous block·next block →recent activity