← previous blocknext block →recent activity
Analyzing
Block #92,211,439
17 transactions · 16 stateful · 2026-08-01 13:14:19 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,211,439 · 17 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
2w03w16w27w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x7239a7a0…e541
0x34b655…2a6f
6 touches
3 conflicts
0xb54facbb…1914
0x34b655…2a6f
6 touches
3 conflicts
0x4755fafb…859b
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
10 conflicts on slot 0xc0eb79d1cb…5529a4
Audit this contract →
← previous block·next block →recent activity