← previous blocknext block →recent activity
Analyzing
Block #100,094,625
26 transactions · 23 stateful · 2026-08-29 04:56:43 UTC
Parallelism
69/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,094,625 · 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
1w02w18w113w214w315w418w519w620w725w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1a3e281…c954
0x34b655…2a6f
14 touches
21 conflicts
0x61571888…b392
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x68e4bc91…ad89
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 0xc1a3e28102…30c954
Audit this contract →
← previous block·next block →recent activity