← previous blocknext block →recent activity
Analyzing
Block #100,699,451
11 transactions · 9 stateful · 2026-08-31 07:43:57 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,699,451 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
2 touches
0 conflicts
0x58888587…bb8d
0x34b655…2a6f
2 touches
0 conflicts
0x59991669…58c6
0x34b655…2a6f
2 touches
0 conflicts
0x7b0297c7…8f17
0x34b655…2a6f
2 touches
0 conflicts
0x7fb99184…e8bb
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity