← previous blocknext block →recent activity
Analyzing
Block #94,302,698
16 transactions · 15 stateful · 2026-08-08 20:41:28 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,302,698 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w29w310w213w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
8 touches
6 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x64ec0eb4…5108
0xa6afd3…d132
7 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x4175950a…1dfe
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity