← previous blocknext block →recent activity
Analyzing
Block #104,166,873
15 transactions · 14 stateful · 2026-09-12 11:23:23 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,166,873 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w010w111w212w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3250389…8774
0x34b655…2a6f
8 touches
6 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
6 touches
3 conflicts
0x6127c8ac…3f6e
0x34b655…2a6f
6 touches
3 conflicts
0xd07dc434…c644
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc1998045…f700
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0xa325038957…7f8774
Audit this contract →
← previous block·next block →recent activity