← previous blocknext block →recent activity
Analyzing
Block #87,663,673
33 transactions · 32 stateful · 2026-07-14 08:26:06 UTC
Parallelism
55/100
Blocked
63%
Avg conflicts / tx
3.52
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,663,673 · 33 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
7w09w010w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1324w1425w126w127w228w331w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72bc40aa…4c4b
0x0a2fbf…29b1
30 touches
105 conflicts
0x00000000…0005
0x370e2e…63b4
30 touches
105 conflicts
0x72bc40aa…4c4c
0x0a2fbf…29b1
30 touches
105 conflicts
0x72bc40aa…4c4f
0x0a2fbf…29b1
30 touches
105 conflicts
0x8bb57615…2a2a
0x0a2fbf…29b1
30 touches
105 conflicts
0x8bb57615…2a2b
0x0a2fbf…29b1
30 touches
105 conflicts
0x1bff683e…7ecb
0x754704…b603
30 touches
105 conflicts
0x00000000…0006
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: 0x0a2fbf2d…f729b1
105 conflicts on slot 0x72bc40aafb…d04c4b
Audit this contract →
← previous block·next block →recent activity