← previous blocknext block →recent activity
Analyzing
Block #100,876,108
18 transactions · 18 stateful · 2026-08-31 22:33:01 UTC
Parallelism
61/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,876,108 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w313w114w015w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x39773cec…38ed
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x74e485b1…d380
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity