← previous blocknext block →recent activity
Analyzing
Block #101,666,998
19 transactions · 19 stateful · 2026-09-03 16:52:21 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,666,998 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w08w19w011w012w114w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb037179f…5b22
0x34b655…2a6f
6 touches
3 conflicts
0xb40e601f…bf98
0x34b655…2a6f
6 touches
3 conflicts
0xbdc97bbb…6c8e
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa2c04336…e4c0
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
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
3 conflicts on slot 0xb037179ff9…de5b22
Audit this contract →
← previous block·next block →recent activity