← previous blocknext block →recent activity
Analyzing
Block #101,673,129
21 transactions · 17 stateful · 2026-09-03 17:23:12 UTC
Parallelism
57/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,673,129 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w010w012w115w316w417w518w619w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x2ac7f66e…e903
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51aa664e…d3b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x58edd443…786c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity