← previous blocknext block →recent activity
Analyzing
Block #100,727,926
19 transactions · 19 stateful · 2026-08-31 10:07:12 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,727,926 · 19 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
2w04w06w17w28w310w417w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x474e5df9…821f
0x851145…3f07
4 touches
1 conflict
0xd97b0449…00a0
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4e20bf58…ba0a
0xd32edf…ff58
3 touches
1 conflict
0x5cc231f5…f1cd
0x34ae4d…3fc5
2 touches
0 conflicts
0x7aa91b8f…d070
0x34ae4d…3fc5
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity