← previous blocknext block →recent activity
Analyzing
Block #90,210,324
23 transactions · 21 stateful · 2026-07-25 13:09:10 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,210,324 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w112w013w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe8d8a9a2…40f3
0x34b655…2a6f
6 touches
3 conflicts
0x73e89276…ffc4
0x34b655…2a6f
6 touches
3 conflicts
0xa4c56761…79e0
0x34b655…2a6f
6 touches
3 conflicts
0x92a5eb10…d5e3
0x34b655…2a6f
6 touches
3 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xb27fa551…a0a6
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity