← previous blocknext block →recent activity
Analyzing
Block #91,129,154
6 transactions · 6 stateful · 2026-07-28 18:27:41 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,129,154 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x9f64b79f…6722
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0x6ffb6fe7…ddc7
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4b
0x34b655…2a6f
2 touches
0 conflicts
0x6effe1b5…32ef
0x34b655…2a6f
2 touches
0 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
2 touches
0 conflicts
0xbf339666…85e5
0x34b655…2a6f
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 0x35b0198ea3…413e0d
Audit this contract →
← previous block·next block →recent activity