← previous blocknext block →recent activity
Analyzing
Block #91,834,354
12 transactions · 11 stateful · 2026-07-31 05:37:36 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,834,354 · 12 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
2w03w14w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe84ca9a7…b041
0x34b655…2a6f
4 touches
1 conflict
0xf0bf41b6…682f
0x34b655…2a6f
4 touches
1 conflict
0x4bccd149…7d0e
0x34b655…2a6f
4 touches
1 conflict
0x9b990b16…5f1c
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
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 0x5655f5c3b4…dd6b75
Audit this contract →
← previous block·next block →recent activity