← previous blocknext block →recent activity
Analyzing
Block #90,823,211
14 transactions · 13 stateful · 2026-07-27 16:47:39 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,823,211 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6e326b…ead3
0x34b655…2a6f
4 touches
1 conflict
0xd7badc5e…8c2b
0xa6afd3…d132
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2e73ed05…be33
0x34b655…2a6f
4 touches
1 conflict
0x330df1e6…7586
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xde6e326b50…50ead3
Audit this contract →
← previous block·next block →recent activity