← previous blocknext block →recent activity
Analyzing
Block #91,293,559
9 transactions · 9 stateful · 2026-07-29 08:15:37 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,293,559 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18316bb4…d507
0x34b655…2a6f
4 touches
1 conflict
0x2a24af1d…7be1
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x365bd58a…0eb5
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0x58fe85be…540f
0x34b655…2a6f
4 touches
1 conflict
0x824a94ee…a634
0x34b655…2a6f
4 touches
1 conflict
0x8db5666d…76f0
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 0x18316bb47a…42d507
Audit this contract →
← previous block·next block →recent activity