← previous blocknext block →recent activity
Analyzing
Block #100,139,614
16 transactions · 15 stateful · 2026-08-29 08:43:23 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,139,614 · 16 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
1w07w18w29w211w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79a2784a…586f
0x34b655…2a6f
8 touches
6 conflicts
0xd5c98027…9fd9
0x34b655…2a6f
6 touches
3 conflicts
0x50c61506…343f
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4846
0x34b655…2a6f
4 touches
1 conflict
0x52cf5603…ca01
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
6 conflicts on slot 0x79a2784aed…66586f
Audit this contract →
← previous block·next block →recent activity