← previous blocknext block →recent activity
Analyzing
Block #90,917,687
14 transactions · 11 stateful · 2026-07-28 00:42:58 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,917,687 · 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
1w02w16w07w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xdfc2c1fb…6dc6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x420dd604…6879
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x6cad9553…19d1
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 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity