← previous blocknext block →recent activity
Analyzing
Block #90,697,859
13 transactions · 13 stateful · 2026-07-27 06:16:56 UTC
Parallelism
46/100
Blocked
62%
Avg conflicts / tx
1.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,697,859 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w17w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x706f6ad1…a172
0x34b655…2a6f
4 touches
1 conflict
0x80404691…4a11
0x34b655…2a6f
4 touches
1 conflict
0x8e572796…0e59
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity