← previous blocknext block →recent activity
Analyzing
Block #100,139,819
24 transactions · 21 stateful · 2026-08-29 08:44:25 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,139,819 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w211w312w414w515w616w720w222w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61e2c349…73aa
0x34b655…2a6f
14 touches
21 conflicts
0x50c61506…343f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe7297800…65cf
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
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 0x61e2c34985…4873aa
Audit this contract →
← previous block·next block →recent activity