← previous blocknext block →recent activity
Analyzing
Block #100,229,977
19 transactions · 19 stateful · 2026-08-29 16:18:16 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,229,977 · 19 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
2w03w16w07w28w310w311w413w114w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c5120ac…af7a
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
21 conflicts on slot 0x2c5120ac14…9daf7a
Audit this contract →
← previous block·next block →recent activity