← previous blocknext block →recent activity
Analyzing
Block #90,386,217
12 transactions · 12 stateful · 2026-07-26 04:02:59 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,386,217 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0153faf…33ca
0x34b655…2a6f
8 touches
6 conflicts
0x6bf457e3…9576
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x33f54bd6…9ac3
0x34b655…2a6f
4 touches
1 conflict
0x3c24a217…2784
0x34b655…2a6f
4 touches
1 conflict
0x529e8f13…967a
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
6 conflicts on slot 0xe0153faf39…5c33ca
Audit this contract →
← previous block·next block →recent activity