← previous blocknext block →recent activity
Analyzing
Block #100,590,830
24 transactions · 19 stateful · 2026-08-30 22:37:33 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,590,830 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w010w311w412w116w417w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f152323…bf26
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0ed724e6…2693
0xd32edf…ff58
7 touches
6 conflicts
0x382434ca…96b5
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0xac389ba9…8b45
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
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
6 conflicts on slot 0x2f1523237e…c8bf26
Audit this contract →
← previous block·next block →recent activity