← previous blocknext block →recent activity
Analyzing
Block #91,396,246
13 transactions · 13 stateful · 2026-07-29 16:52:22 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,396,246 · 13 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
2w03w14w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d71b10a…bb5e
0x7b9256…1fb2
4 touches
1 conflict
0x5d71b10a…bb61
0x7b9256…1fb2
4 touches
1 conflict
0x62422816…47ec
0x7b9256…1fb2
4 touches
1 conflict
0x62422816…47ed
0x7b9256…1fb2
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0dfd824…79a6
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x5d71b10a05…b0bb5e
Audit this contract →
← previous block·next block →recent activity