← previous blocknext block →recent activity
Analyzing
Block #93,457,301
21 transactions · 17 stateful · 2026-08-05 21:42:55 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,457,301 · 21 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
3w04w18w09w110w213w014w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd87a64…6651
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa5b2d571…e945
0x99c7a7…8bf0
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf454cca7…095a
0x34b655…2a6f
4 touches
1 conflict
0x1ea2c53b…887a
0x754704…b603
4 touches
1 conflict
0x2edbccf6…cc14
0x754704…b603
4 touches
1 conflict
0x768de509…bf9b
0x754704…b603
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
3 conflicts on slot 0x0fd87a64db…786651
Audit this contract →
← previous block·next block →recent activity