← previous blocknext block →recent activity
Analyzing
Block #91,119,026
11 transactions · 10 stateful · 2026-07-28 17:36:44 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,119,026 · 11 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
1w03w14w05w16w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8530f3c4…b9cc
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb064a9d2…a1a9
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x890a1db9…1712
0xa6afd3…d132
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 0x8530f3c49c…3eb9cc
Audit this contract →
← previous block·next block →recent activity