← previous blocknext block →recent activity
Analyzing
Block #90,854,162
7 transactions · 6 stateful · 2026-07-27 19:23:20 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,854,162 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24eaf46d…8c2e
0x34b655…2a6f
4 touches
1 conflict
0x7b0665e8…fbdf
0x34b655…2a6f
4 touches
1 conflict
0x89f02b88…4704
0x34b655…2a6f
4 touches
1 conflict
0xa2fb11b5…082c
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0xc694d6ac…8d36
0x34b655…2a6f
4 touches
1 conflict
0xd7d20b6c…611f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x24eaf46d19…768c2e
Audit this contract →
← previous block·next block →recent activity