← previous blocknext block →recent activity
Analyzing
Block #90,796,442
22 transactions · 17 stateful · 2026-07-27 14:32:53 UTC
Parallelism
64/100
Blocked
53%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,796,442 · 22 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
1w02w17w08w19w210w311w412w513w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x33967383…de4d
0x34b655…2a6f
6 touches
3 conflicts
0x26926b58…e414
0x34b655…2a6f
4 touches
1 conflict
0x2ac796c1…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x2b5ab9a3…58c5
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x45ef9175…5ab2
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity