← previous blocknext block →recent activity
Analyzing
Block #91,269,635
7 transactions · 6 stateful · 2026-07-29 06:14:55 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,269,635 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x387ada6b…994f
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xbe7e2fe0…1288
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x079bf666…56c4
0x34b655…2a6f
2 touches
0 conflicts
0x10efb0c1…2ddc
0x34b655…2a6f
2 touches
0 conflicts
0x11d10d93…10d5
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 0x387ada6b1b…a3994f
Audit this contract →
← previous block·next block →recent activity