← previous blocknext block →recent activity
Analyzing
Block #90,233,284
19 transactions · 18 stateful · 2026-07-25 15:04:57 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,233,284 · 19 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
1w05w06w18w211w312w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0101660…ca43
0x34b655…2a6f
6 touches
3 conflicts
0x5df7cf2b…bbe5
0x34b655…2a6f
6 touches
3 conflicts
0x0494220d…abf6
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x53631cb7…eb14
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
3 conflicts on slot 0xf0101660f7…27ca43
Audit this contract →
← previous block·next block →recent activity