← previous blocknext block →recent activity
Analyzing
Block #91,984,954
13 transactions · 12 stateful · 2026-07-31 18:15:15 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,984,954 · 13 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
1w03w04w17w08w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x849c2133…33c6
0x34b655…2a6f
6 touches
3 conflicts
0xea93a1f8…ef0c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x27581e23…05f3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9de95c94…61c3
0x34b655…2a6f
4 touches
1 conflict
0xb25fa8e2…c9ef
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x849c21338c…9f33c6
Audit this contract →
← previous block·next block →recent activity