← previous blocknext block →recent activity
Analyzing
Block #93,372,106
20 transactions · 19 stateful · 2026-08-05 14:34:36 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,372,106 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w39w410w011w112w214w515w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd12b6c…02cc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x24933e74…db08
0x34b655…2a6f
6 touches
3 conflicts
0xcd99f3ef…e2c7
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0xab12f729…f0ff
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
21 conflicts on slot 0x2fd12b6c73…8702cc
Audit this contract →
← previous block·next block →recent activity