← previous blocknext block →recent activity
Analyzing
Block #90,856,214
12 transactions · 11 stateful · 2026-07-27 19:33:39 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,856,214 · 12 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
1w02w03w04w15w26w27w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecfe09ea…21d2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdb3937e8…23cb
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x1beb81a6…c40d
0x34b655…2a6f
4 touches
1 conflict
0x46d6bfe6…5b21
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 0xecfe09ea82…8c21d2
Audit this contract →
← previous block·next block →recent activity