← previous blocknext block →recent activity
Analyzing
Block #100,602,064
19 transactions · 18 stateful · 2026-08-30 23:34:04 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,602,064 · 19 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
1w02w13w24w37w48w09w110w511w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff7cb355…3404
0x34b655…2a6f
6 touches
3 conflicts
0x2ea68a12…cc8d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x035d2618…ccac
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xff7cb355cf…973404
Audit this contract →
← previous block·next block →recent activity