← previous blocknext block →recent activity
Analyzing
Block #101,667,590
19 transactions · 15 stateful · 2026-09-03 16:55:20 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,667,590 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w412w513w616w018w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x2d93833d…aa1e
0x34b655…2a6f
6 touches
3 conflicts
0x885efce3…7496
0x34b655…2a6f
6 touches
3 conflicts
0xee799cea…1f1c
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x5a22f456…b743
0x34b655…2a6f
4 touches
1 conflict
0x87c0726b…5b33
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity