← previous blocknext block →recent activity
Analyzing
Block #100,063,731
18 transactions · 17 stateful · 2026-08-29 02:21:11 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
2.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,063,731 · 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
1w02w13w24w05w06w17w28w310w411w513w614w715w717w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98c943e…7c44
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x71ee1cd9…f4dd
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x664fee5f…554b
0x34b655…2a6f
8 touches
6 conflicts
0x615e7c53…e353
0x34b655…2a6f
7 touches
6 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
28 conflicts on slot 0xf98c943e1d…327c44
Audit this contract →
← previous block·next block →recent activity