← previous blocknext block →recent activity
Analyzing
Block #92,601,160
11 transactions · 10 stateful · 2026-08-02 21:54:21 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,601,160 · 11 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18e6b1c8…8a45
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2f4973fd…3c87
0xd32edf…ff58
3 touches
1 conflict
0x15041e24…a7b8
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
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
1 conflict on slot 0x18e6b1c856…258a45
Audit this contract →
← previous block·next block →recent activity