← previous blocknext block →recent activity
Analyzing
Block #89,697,078
38 transactions · 37 stateful · 2026-07-23 17:59:33 UTC
Parallelism
60/100
Blocked
65%
Avg conflicts / tx
3.39
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,697,078 · 38 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w08w09w110w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1326w127w228w233w336w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
30 touches
105 conflicts
0x1bff683e…7ecb
0x754704…b603
30 touches
105 conflicts
0x55b4e430…44cb
0x754704…b603
30 touches
105 conflicts
0x00000000…0006
0x0a2fbf…29b1
30 touches
105 conflicts
0x3255cba4…43a6
0x0a2fbf…29b1
30 touches
105 conflicts
0x3255cba4…43a7
0x0a2fbf…29b1
30 touches
105 conflicts
0x3255cba4…43aa
0x0a2fbf…29b1
30 touches
105 conflicts
0x7eac25b0…1a98
0x0a2fbf…29b1
30 touches
105 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: 0x370e2ee6…bd63b4
105 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity