← previous blocknext block →recent activity
Analyzing
Block #101,016,404
25 transactions · 25 stateful · 2026-09-01 10:18:48 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,016,404 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w010w111w212w313w414w416w518w619w522w023w124w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c0e1ae4…59f1
0x34b655…2a6f
10 touches
10 conflicts
0x5a8156fe…4c08
0x34b655…2a6f
10 touches
10 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x086e15c2…1796
0x34b655…2a6f
6 touches
3 conflicts
0x17d75238…7d7c
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
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
10 conflicts on slot 0x3c0e1ae47f…0359f1
Audit this contract →
← previous block·next block →recent activity