← previous blocknext block →recent activity
Analyzing
Block #100,231,703
23 transactions · 18 stateful · 2026-08-29 16:26:57 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,231,703 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w113w015w116w218w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40fa8a7…a319
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
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 0xc40fa8a7a4…d2a319
Audit this contract →
← previous block·next block →recent activity