← previous blocknext block →recent activity
Analyzing
Block #91,008,615
16 transactions · 13 stateful · 2026-07-28 08:21:04 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,008,615 · 16 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
5w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe64d2555…8caf
0x34b655…2a6f
4 touches
1 conflict
0x2694a96c…1d74
0x065c9d…c394
2 touches
0 conflicts
0x28bd984c…c77f
0x065c9d…c394
2 touches
0 conflicts
0x3b31f37e…cb40
0x065c9d…c394
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 0x37d710c811…2145c1
Audit this contract →
← previous block·next block →recent activity