← previous blocknext block →recent activity
Analyzing
Block #92,768,379
23 transactions · 22 stateful · 2026-08-03 11:56:35 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,768,379 · 23 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
1w02w13w04w05w16w18w010w211w014w117w018w119w220w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9f
0x2b46c0…1669
4 touches
1 conflict
0xea8e47b0…abfe
0x2b46c0…1669
4 touches
1 conflict
0xf1a14809…56fd
0x2b46c0…1669
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity