← previous blocknext block →recent activity
Analyzing
Block #90,428,101
9 transactions · 8 stateful · 2026-07-26 07:38:14 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,428,101 · 9 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0x64687417…8d60
0x34b655…2a6f
4 touches
1 conflict
0xb3ae4660…5f75
0x34b655…2a6f
4 touches
1 conflict
0x04bc2872…351a
0x34b655…2a6f
3 touches
1 conflict
0x08d3a793…99dc
0x34b655…2a6f
2 touches
0 conflicts
0x0a6c31fc…f4c3
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6a
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 0x5a36d0c873…e212e2
Audit this contract →
← previous block·next block →recent activity