← previous blocknext block →recent activity
Analyzing
Block #91,075,627
14 transactions · 12 stateful · 2026-07-28 13:58:20 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,075,627 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x97216283…fd1d
0x34b655…2a6f
4 touches
1 conflict
0x514e8c17…48c0
0x34b655…2a6f
4 touches
1 conflict
0x363f99e4…32c8
0x34b655…2a6f
2 touches
0 conflicts
0x45f1ce4c…14f9
0x34b655…2a6f
2 touches
0 conflicts
0x48315f67…c1a6
0x34b655…2a6f
2 touches
0 conflicts
0x570cf945…ce1d
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity