← previous blocknext block →recent activity
Analyzing
Block #90,386,621
21 transactions · 19 stateful · 2026-07-26 04:05:03 UTC
Parallelism
62/100
Blocked
37%
Avg conflicts / tx
0.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,386,621 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w210w311w413w518w019w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7907f7f7…dc3f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
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 0x7907f7f764…8adc3f
Audit this contract →
← previous block·next block →recent activity