← previous blocknext block →recent activity
Analyzing
Block #94,320,126
18 transactions · 15 stateful · 2026-08-08 22:09:55 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,320,126 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w28w39w010w111w212w214w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x64e5f38d…187c
0x34b655…2a6f
4 touches
1 conflict
0x8b79405f…10a2
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity