← previous blocknext block →recent activity
Analyzing
Block #90,864,139
10 transactions · 9 stateful · 2026-07-27 20:13:34 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,864,139 · 10 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
2w03w04w15w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0xad4ad7e6…f605
0x34b655…2a6f
4 touches
1 conflict
0xb027a20d…5efe
0x34b655…2a6f
4 touches
1 conflict
0xba6ecb35…8e56
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x471515c5…322a
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 0x757b054398…dbe087
Audit this contract →
← previous block·next block →recent activity