← previous blocknext block →recent activity
Analyzing
Block #90,796,489
22 transactions · 18 stateful · 2026-07-27 14:33:07 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,796,489 · 22 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
3w04w15w26w37w012w114w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x55012d1a…3907
0x2b46c0…1669
4 touches
1 conflict
0xa987699f…eabe
0x2b46c0…1669
4 touches
1 conflict
0xad3ef711…4f2b
0x2b46c0…1669
4 touches
1 conflict
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0x05c3bda4…de90
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity