← previous blocknext block →recent activity
Analyzing
Block #90,540,709
18 transactions · 14 stateful · 2026-07-26 17:06:21 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,540,709 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w09w010w111w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0xd876b049…2927
0x34b655…2a6f
6 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
4 touches
1 conflict
0x1c9ee5c7…0329
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
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
3 conflicts on slot 0x25957369b1…4cc648
Audit this contract →
← previous block·next block →recent activity