← previous blocknext block →recent activity
Analyzing
Block #100,739,506
30 transactions · 29 stateful · 2026-08-31 11:05:27 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,739,506 · 30 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
1w02w16w07w18w29w310w211w315w416w423w224w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4031b3d0…9908
0x34b655…2a6f
8 touches
6 conflicts
0x7c4836dd…31d9
0x851145…3f07
7 touches
6 conflicts
0xca841faa…486a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity