← previous blocknext block →recent activity
Analyzing
Block #92,172,807
18 transactions · 16 stateful · 2026-08-01 10:00:03 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,172,807 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w09w010w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x46279ae7…20dd
0x2b46c0…1669
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
4 touches
1 conflict
0x0f427418…2a49
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
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
3 conflicts on slot 0x92115abda4…1fad76
Audit this contract →
← previous block·next block →recent activity