← previous blocknext block →recent activity
Analyzing
Block #91,070,130
15 transactions · 14 stateful · 2026-07-28 13:30:41 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,070,130 · 15 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
4w05w17w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbc1fffc…2888
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x19d0122b…937c
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfd446…43f8
0x34b655…2a6f
2 touches
0 conflicts
0x42b5d7b8…e7a8
0x34b655…2a6f
2 touches
0 conflicts
0x43915ca6…bd77
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 0xdbc1fffcfe…552888
Audit this contract →
← previous block·next block →recent activity