← previous blocknext block →recent activity
Analyzing
Block #88,083,004
33 transactions · 32 stateful · 2026-07-16 07:11:05 UTC
Parallelism
55/100
Blocked
59%
Avg conflicts / tx
3.21
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #88,083,004 · 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
1w04w05w17w09w110w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1325w126w128w229w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda82a210…1c1b
0x0a2fbf…29b1
28 touches
91 conflicts
0xd2253aeb…c307
0x0a2fbf…29b1
28 touches
91 conflicts
0x00000000…0005
0x370e2e…63b4
28 touches
91 conflicts
0xd2253aeb…c308
0x0a2fbf…29b1
28 touches
91 conflicts
0xda82a210…1c1a
0x0a2fbf…29b1
28 touches
91 conflicts
0xda82a210…1c1e
0x0a2fbf…29b1
28 touches
91 conflicts
0x1bff683e…7ecb
0x754704…b603
28 touches
91 conflicts
0x55b4e430…44cb
0x754704…b603
28 touches
91 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
91 conflicts on slot 0xda82a210bc…dd1c1b
Audit this contract →
← previous block·next block →recent activity