← previous blocknext block →recent activity
Analyzing
Block #89,849,924
19 transactions · 18 stateful · 2026-07-24 06:50:59 UTC
Parallelism
84/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,849,924 · 19 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
1w02w16w07w19w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfb53ecf8…bd11
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x30a8ba72…0263
0x0a2fbf…29b1
4 touches
1 conflict
0xcd9f93a5…9a93
0x0a2fbf…29b1
4 touches
1 conflict
0xcd9f93a5…9a94
0x0a2fbf…29b1
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity