← previous blocknext block →recent activity
Analyzing
Block #94,467,306
19 transactions · 18 stateful · 2026-08-09 10:38:06 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,467,306 · 19 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
4w07w18w29w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
12 touches
15 conflicts
0x00000000…0008
0x0ea966…0742
12 touches
15 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
12 touches
15 conflicts
0x0360769a…ad48
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x83da2486…8024
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: 0xe4f6e757…919657
15 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity