← previous blocknext block →recent activity
Analyzing
Block #100,591,510
21 transactions · 18 stateful · 2026-08-30 22:40:58 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,591,510 · 21 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
8w09w111w213w014w115w016w217w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c6a9da2…c628
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xded216ce…191a
0xa6afd3…d132
6 touches
3 conflicts
0xa8ccb69d…dbff
0x34b655…2a6f
6 touches
3 conflicts
0xab27ee85…deb7
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xb55f6c75…c2d2
0xa6afd3…d132
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 0x9c6a9da253…d0c628
Audit this contract →
← previous block·next block →recent activity