← previous blocknext block →recent activity
Analyzing
Block #92,059,303
13 transactions · 13 stateful · 2026-08-01 00:29:11 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,059,303 · 13 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
5w06w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae4a282a…f2ea
0x34b655…2a6f
4 touches
1 conflict
0xbb4a7ffe…6b61
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdccec60b…687a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d4
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
1 conflict on slot 0xae4a282a40…25f2ea
Audit this contract →
← previous block·next block →recent activity