← previous blocknext block →recent activity
Analyzing
Block #100,024,056
16 transactions · 15 stateful · 2026-08-28 23:01:29 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,024,056 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x14c85e43…fdc4
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x290abc80…f606
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0x9210e826c8…c41414
Audit this contract →
← previous block·next block →recent activity