← previous blocknext block →recent activity
Analyzing
Block #92,420,334
14 transactions · 11 stateful · 2026-08-02 06:44:52 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,420,334 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w17w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x356b3121…cf1c
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x1da7723c…80aa
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x356b3121c7…a1cf1c
Audit this contract →
← previous block·next block →recent activity