← previous blocknext block →recent activity
Analyzing
Block #91,128,845
8 transactions · 7 stateful · 2026-07-28 18:26:08 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,128,845 · 8 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
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x58ae9c0f…d6c8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x3b31f37e…cb40
0x065c9d…c394
2 touches
0 conflicts
0x57945910…12fd
0x065c9d…c394
2 touches
0 conflicts
0x619af9e9…7ebb
0x065c9d…c394
2 touches
0 conflicts
0x7044157b…df13
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 0x1d9867ade5…7b6d9a
Audit this contract →
← previous block·next block →recent activity