← previous blocknext block →recent activity
Analyzing
Block #90,437,085
12 transactions · 11 stateful · 2026-07-26 08:24:29 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,437,085 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7560
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7561
0x34b655…2a6f
4 touches
1 conflict
0x14c4e3ca…edd9
0x34b655…2a6f
4 touches
1 conflict
0x14c4e3ca…edda
0x34b655…2a6f
4 touches
1 conflict
0x2e19029d…72a7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
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
1 conflict on slot 0xd5c98027d8…499fd9
Audit this contract →
← previous block·next block →recent activity