← previous blocknext block →recent activity
Analyzing
Block #91,025,714
6 transactions · 6 stateful · 2026-07-28 09:47:14 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,025,714 · 6 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7a4f47ac…3289
0x34b655…2a6f
4 touches
1 conflict
0x86a2e799…7474
0x34b655…2a6f
4 touches
1 conflict
0x01c23f23…88f4
0x34b655…2a6f
2 touches
0 conflicts
0x03fe94de…ffc8
0x34b655…2a6f
2 touches
0 conflicts
0x0ddf8d9a…405f
0x34b655…2a6f
2 touches
0 conflicts
0x0ea00063…777f
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 0x3bdd71a21a…eeb6eb
Audit this contract →
← previous block·next block →recent activity