← previous blocknext block →recent activity
Analyzing
Block #91,967,020
19 transactions · 18 stateful · 2026-07-31 16:45:03 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,967,020 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w311w412w515w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdbe6b59…f6d8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x91f7608d…d318
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xbdbe6b59da…0cf6d8
Audit this contract →
← previous block·next block →recent activity