← previous blocknext block →recent activity
Analyzing
Block #101,656,857
21 transactions · 19 stateful · 2026-09-03 16:01:20 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,656,857 · 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
2w03w14w05w16w07w18w29w314w315w418w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd366e32f…ec19
0xa7283d…0ace
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x536e2740…61ac
0x3bd359…433a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x8fa7a69c…8fd7
0x7b5b07…6d63
6 touches
3 conflicts
0x00000000…0002
0xa7283d…0ace
6 touches
3 conflicts
0xd366e32f…ec16
0xa7283d…0ace
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity