← previous blocknext block →recent activity
Analyzing
Block #100,066,104
26 transactions · 24 stateful · 2026-08-29 02:33:07 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,066,104 · 26 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
2w04w05w16w29w110w211w313w414w515w616w718w419w524w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc500b1…55cd
0x34b655…2a6f
12 touches
15 conflicts
0x5060cdde…445d
0x34b655…2a6f
10 touches
10 conflicts
0xdd5a06f0…6ccd
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0xd99d25df…ecd8
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
15 conflicts on slot 0x6cc500b1da…a855cd
Audit this contract →
← previous block·next block →recent activity