← previous blocknext block →recent activity
Analyzing
Block #101,816,780
20 transactions · 18 stateful · 2026-09-04 05:25:43 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,816,780 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w113w415w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ba56d60…09dc
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfa44f1db…0666
0x34b655…2a6f
6 touches
3 conflicts
0x86d7c9d4…a62d
0x34b655…2a6f
6 touches
3 conflicts
0x5e3090f2…00cc
0x34b655…2a6f
6 touches
3 conflicts
0x0145aa28…106b
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 0x2ba56d6093…1b09dc
Audit this contract →
← previous block·next block →recent activity