← previous blocknext block →recent activity
Analyzing
Block #91,557,909
16 transactions · 11 stateful · 2026-07-30 06:26:58 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,557,909 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9de5e3de…d010
0x34b655…2a6f
4 touches
1 conflict
0x9ef0b0f7…2508
0x34b655…2a6f
4 touches
1 conflict
0xa139e1f5…bed2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac9a428b…8c14
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
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 0x9de5e3dea2…b4d010
Audit this contract →
← previous block·next block →recent activity