← previous blocknext block →recent activity
Analyzing
Block #100,082,191
18 transactions · 17 stateful · 2026-08-29 03:54:07 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,082,191 · 18 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
1w02w13w05w16w27w38w411w513w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe21a94dd…4838
0x34b655…2a6f
10 touches
11 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
4 conflicts
0x627738d1…db02
0x34b655…2a6f
6 touches
3 conflicts
0x53c0fef6…250b
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
21 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity