← previous blocknext block →recent activity
Analyzing
Block #94,868,758
14 transactions · 14 stateful · 2026-08-10 20:18:54 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,868,758 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fab7fbe…1ce5
0x34b655…2a6f
6 touches
3 conflicts
0x62a8dd5f…3664
0x34b655…2a6f
4 touches
1 conflict
0x8435cea0…f5b6
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x39fb42f2…35f2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfe3f7bde…899b
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 0x5fab7fbe22…391ce5
Audit this contract →
← previous block·next block →recent activity