← previous blocknext block →recent activity
Analyzing
Block #91,445,210
16 transactions · 16 stateful · 2026-07-29 20:59:58 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,445,210 · 16 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
1w02w04w16w17w09w112w213w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x087d9a59…17d7
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x35725dab…9f7b
0x34b655…2a6f
4 touches
1 conflict
0x38e39eef…50bd
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x521a91b0…b4c9
0x34b655…2a6f
4 touches
1 conflict
0x5a310d83…cae0
0x34b655…2a6f
4 touches
1 conflict
0x6fc33cff…b7b5
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 0x087d9a5968…7117d7
Audit this contract →
← previous block·next block →recent activity