← previous blocknext block →recent activity
Analyzing
Block #90,698,949
9 transactions · 7 stateful · 2026-07-27 06:22:25 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,698,949 · 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56b390b…e0ce
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x18bf47fa…4ae5
0x34b655…2a6f
4 touches
1 conflict
0xf4bd9d9f…3317
0x34b655…2a6f
4 touches
1 conflict
0x6c6dcf34…6eb6
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x5bc6b706…fce6
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0xc56b390bd8…6be0ce
Audit this contract →
← previous block·next block →recent activity