← previous blocknext block →recent activity
Analyzing
Block #100,103,863
20 transactions · 19 stateful · 2026-08-29 05:43:14 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,103,863 · 20 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
2w03w04w16w07w111w212w313w414w515w617w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c070aa…40c8
0x34b655…2a6f
14 touches
21 conflicts
0xd895ee0b…d301
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0xa03ad25f…81e5
0x34b655…2a6f
6 touches
3 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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
21 conflicts on slot 0x86c070aa21…4140c8
Audit this contract →
← previous block·next block →recent activity