← previous blocknext block →recent activity
Analyzing
Block #90,542,032
16 transactions · 16 stateful · 2026-07-26 17:13:01 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,542,032 · 16 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
3w04w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf41339fe…d446
0x34b655…2a6f
4 touches
1 conflict
0xd26ec132…35c8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc8c8bf01…e037
0xe52b14…7230
3 touches
1 conflict
0x29a2aad6…286b
0x34b655…2a6f
2 touches
0 conflicts
0x310afe2c…83e1
0x34b655…2a6f
2 touches
0 conflicts
0x3230413b…bc7f
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 0xf41339fe9f…fad446
Audit this contract →
← previous block·next block →recent activity