← previous blocknext block →recent activity
Analyzing
Block #94,196,321
16 transactions · 13 stateful · 2026-08-08 11:42:28 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,196,321 · 16 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
1w02w04w05w16w28w09w111w212w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x12d867cc…b97c
0x34b655…2a6f
4 touches
1 conflict
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity