← previous blocknext block →recent activity
Analyzing
Block #100,108,146
59 transactions · 52 stateful · 2026-08-29 06:04:48 UTC
Parallelism
81/100
Blocked
67%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,108,146 · 59 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w18w09w010w113w016w117w118w220w221w322w034w135w236w137w142w444w548w258w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
22 touches
55 conflicts
0xf3d10975…0d07
0x34b655…2a6f
20 touches
45 conflicts
0xea02471d…1542
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
16 touches
28 conflicts
0xb9868b52…c77f
0x34b655…2a6f
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 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: 0xf5b5f7f8…a36d70
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity