← previous blocknext block →recent activity
Analyzing
Block #90,510,218
11 transactions · 10 stateful · 2026-07-26 14:33:00 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,510,218 · 11 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x5a39b4fb…266f
0x34b655…2a6f
4 touches
1 conflict
0x8ae3e2cf…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xd5d0b681…ca6c
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x0c9e9b1d…bc44
0x34b655…2a6f
2 touches
0 conflicts
0x0c9e9b1d…bc45
0x34b655…2a6f
2 touches
0 conflicts
0x11fdc1b8…573f
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity