← previous blocknext block →recent activity
Analyzing
Block #89,847,401
12 transactions · 9 stateful · 2026-07-24 06:38:17 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,847,401 · 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
1w02w13w24w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf79c54f3…c0c1
0x34b655…2a6f
4 touches
1 conflict
0x4b1134d6…20c9
0x34b655…2a6f
4 touches
1 conflict
0xebc8c0af…c329
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x3714f868…591c
0x0594c7…a3be
2 touches
0 conflicts
0xb0113590…5554
0x0594c7…a3be
2 touches
0 conflicts
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity