← previous blocknext block →recent activity
Analyzing
Block #90,291,153
16 transactions · 16 stateful · 2026-07-25 19:57:18 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,291,153 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w08w19w211w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0a04fe8…f08c
0x34b655…2a6f
6 touches
3 conflicts
0xe19cbaaf…3b90
0x34b655…2a6f
4 touches
1 conflict
0xef1de905…0582
0x34b655…2a6f
4 touches
1 conflict
0xff8b4178…773d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x34933aba…06e4
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
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 0xe0a04fe8ef…d4f08c
Audit this contract →
← previous block·next block →recent activity