← previous blocknext block →recent activity
Analyzing
Block #90,855,316
15 transactions · 14 stateful · 2026-07-27 19:29:08 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,855,316 · 15 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
2w07w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0xb8190eb7…5574
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x35177414…c40a
0x34b655…2a6f
2 touches
0 conflicts
0xca608d0c…f23b
0x34b655…2a6f
2 touches
0 conflicts
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 0x5fde497131…e8aac9
Audit this contract →
← previous block·next block →recent activity