← previous blocknext block →recent activity
Analyzing
Block #91,834,291
19 transactions · 16 stateful · 2026-07-31 05:37:17 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,834,291 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0x3e4af36e…07ae
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6381d47e…0209
0x34b655…2a6f
4 touches
1 conflict
0x65f90aa4…c97f
0x34b655…2a6f
4 touches
1 conflict
0x6cb0a69c…ab30
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity