← previous blocknext block →recent activity
Analyzing
Block #91,445,353
28 transactions · 24 stateful · 2026-07-29 21:00:41 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,445,353 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w410w011w112w213w315w216w117w319w323w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8509f0e0…2419
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xcf8e8419…c691
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity