← previous blocknext block →recent activity
Analyzing
Block #100,703,817
55 transactions · 39 stateful · 2026-08-31 08:05:54 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
2.07
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #100,703,817 · 55 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w119w220w321w422w526w327w428w529w634w738w839w940w942w343w1044w1145w246w351w1254w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xf8e6479f…f193
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x297de2d5…7396
0x34b655…2a6f
12 touches
15 conflicts
0x8996e3d7…5c24
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbe11ef64…754d
0x34b655…2a6f
8 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity