← previous blocknext block →recent activity
Analyzing
Block #100,432,417
23 transactions · 20 stateful · 2026-08-30 09:20:33 UTC
Parallelism
74/100
Blocked
30%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,432,417 · 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
4w09w110w211w314w417w520w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x20fcad1f…1d7d
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe6b17482…3957
0x34b655…2a6f
4 touches
1 conflict
0x212a19ca…2dd4
0x34b655…2a6f
4 touches
1 conflict
0x289ce6b2…d0ae
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
15 conflicts on slot 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity