← previous blocknext block →recent activity
Analyzing
Block #100,747,736
23 transactions · 23 stateful · 2026-08-31 11:46:50 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,747,736 · 23 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
1w02w04w15w16w28w19w211w312w313w414w015w116w217w320w522w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xf741ea6a…dc90
0x851145…3f07
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0d3ea414…235a
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 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity