← previous blocknext block →recent activity
Analyzing
Block #90,960,301
14 transactions · 12 stateful · 2026-07-28 04:17:17 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,960,301 · 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
5w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16f8e14a…f6e4
0x34b655…2a6f
2 touches
0 conflicts
0x18283fbb…cc97
0x34b655…2a6f
2 touches
0 conflicts
0x1becedd5…42e3
0x34b655…2a6f
2 touches
0 conflicts
0x1de6e314…2416
0x34b655…2a6f
2 touches
0 conflicts
0x200ed648…912f
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity