← previous blocknext block →recent activity
Analyzing
Block #90,890,545
20 transactions · 19 stateful · 2026-07-27 22:26:24 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,890,545 · 20 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
3w04w17w08w29w310w111w312w414w015w116w218w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadaf61be…38bd
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x3d2c514e…49b1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c6085…e8a1
0x34b655…2a6f
6 touches
3 conflicts
0x1a8e09ea…23cc
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xadaf61be4d…b838bd
Audit this contract →
← previous block·next block →recent activity