← previous blocknext block →recent activity
Analyzing
Block #100,132,712
19 transactions · 17 stateful · 2026-08-29 08:08:30 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,132,712 · 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
2w03w15w06w17w08w19w212w315w416w517w418w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x944a1493…fdd4
0x34b655…2a6f
6 touches
3 conflicts
0xfc81faf7…1417
0x34b655…2a6f
6 touches
3 conflicts
0x52cef1b0…0e4e
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity