← previous blocknext block →recent activity
Analyzing
Block #90,808,294
14 transactions · 13 stateful · 2026-07-27 15:32:31 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,808,294 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed81edac…d50f
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x223caa2c…e97f
0x34b655…2a6f
4 touches
1 conflict
0x42c51fbb…4575
0x34b655…2a6f
4 touches
1 conflict
0x6723c3a2…8b22
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x6ec11f62…98a6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xed81edac6f…e0d50f
Audit this contract →
← previous block·next block →recent activity