← previous blocknext block →recent activity
Analyzing
Block #100,619,254
21 transactions · 18 stateful · 2026-08-31 01:00:33 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,619,254 · 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
1w02w17w29w210w313w014w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
10 touches
10 conflicts
0x46f78cfd…3f67
0x34b655…2a6f
6 touches
3 conflicts
0xd6d356ab…4590
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc45e4fb5…7cc3
0xa6afd3…d132
4 touches
1 conflict
0xa6d40b7f…2969
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
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
10 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity