← previous blocknext block →recent activity
Analyzing
Block #90,700,245
15 transactions · 14 stateful · 2026-07-27 06:28:56 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,700,245 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4ca2a6c3…ab80
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x901dd65e…5787
0x34b655…2a6f
6 touches
3 conflicts
0x4e37574f…4145
0x34b655…2a6f
6 touches
3 conflicts
0x65104f89…bbce
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7f4112e1…012a
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity