← previous blocknext block →recent activity
Analyzing
Block #91,089,941
14 transactions · 12 stateful · 2026-07-28 15:10:24 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,089,941 · 14 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
4w08w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa68dfacc…cdb8
0x34b655…2a6f
4 touches
1 conflict
0xd4dfefe7…b85f
0x34b655…2a6f
4 touches
1 conflict
0xd957c18f…5cfc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3e6c02a…d3d4
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0a07805e…94a5
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: Perpl
1 conflict on slot 0xa68dfacc6a…72cdb8
Audit this contract →
← previous block·next block →recent activity