← previous blocknext block →recent activity
Analyzing
Block #100,048,172
17 transactions · 16 stateful · 2026-08-29 01:02:52 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,048,172 · 17 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
2w06w18w29w310w411w512w213w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24bb46f7…3853
0x34b655…2a6f
14 touches
21 conflicts
0xfdafaeb3…4b67
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5312402f…0d71
0x34b655…2a6f
6 touches
3 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
6 touches
3 conflicts
0x15b5f87e…b707
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0x24bb46f739…c13853
Audit this contract →
← previous block·next block →recent activity