← previous blocknext block →recent activity
Analyzing
Block #101,022,257
19 transactions · 17 stateful · 2026-09-01 10:48:15 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,022,257 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w29w310w411w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef70a96…db44
0x34b655…2a6f
10 touches
10 conflicts
0x786d8c6c…a2e7
0x34b655…2a6f
10 touches
10 conflicts
0x41c52e32…c46a
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0xff23048d…55d1
0x34b655…2a6f
8 touches
6 conflicts
0xd895ee0b…d301
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004f
0x80c745…7210
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 0xcef70a965c…28db44
Audit this contract →
← previous block·next block →recent activity