← previous blocknext block →recent activity
Analyzing
Block #100,145,051
26 transactions · 24 stateful · 2026-08-29 09:10:46 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,145,051 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w09w110w211w212w113w114w218w220w221w322w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity