← previous blocknext block →recent activity
Analyzing
Block #90,637,234
11 transactions · 11 stateful · 2026-07-27 01:11:57 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,637,234 · 11 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
1w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53699236…fede
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa8590d68…d5c8
0x34b655…2a6f
4 touches
1 conflict
0xddcc4b6f…e15b
0x34b655…2a6f
4 touches
1 conflict
0x331eb8c3…e3de
0x34b655…2a6f
2 touches
0 conflicts
0x3371a69b…441e
0x34b655…2a6f
2 touches
0 conflicts
0x462c0b5f…aa56
0x34b655…2a6f
2 touches
0 conflicts
0x4ccb5334…7c73
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 0x53699236c4…57fede
Audit this contract →
← previous block·next block →recent activity