← previous blocknext block →recent activity
Analyzing
Block #100,144,521
19 transactions · 15 stateful · 2026-08-29 09:08:06 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,144,521 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w08w112w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeab71d04…e42a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
8 touches
6 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
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 0xeab71d04cf…a6e42a
Audit this contract →
← previous block·next block →recent activity