← previous blocknext block →recent activity
Analyzing
Block #90,808,413
15 transactions · 14 stateful · 2026-07-27 15:33:07 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,808,413 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w29w310w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xac62ede4…57c1
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x3ee9e6d7…0c00
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity