← previous blocknext block →recent activity
Analyzing
Block #90,706,378
18 transactions · 18 stateful · 2026-07-27 06:59:47 UTC
Parallelism
61/100
Blocked
33%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,706,378 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w29w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xae520586…087f
0x34b655…2a6f
8 touches
6 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
0xe2b83cd7…4fb4
0x34b655…2a6f
6 touches
3 conflicts
0x6f988a4a…b39f
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity