← previous blocknext block →recent activity
Analyzing
Block #91,780,107
23 transactions · 21 stateful · 2026-07-31 01:04:42 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,780,107 · 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
4w05w16w07w18w29w010w211w115w016w119w220w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0x90691eea…c613
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 0x8218911eb6…d93bed
Audit this contract →
← previous block·next block →recent activity