← previous blocknext block →recent activity
Analyzing
Block #101,802,478
18 transactions · 17 stateful · 2026-09-04 04:13:47 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,802,478 · 18 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
1w02w13w27w113w216w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca70fa2c…6a7e
0x34b655…2a6f
8 touches
6 conflicts
0xc7d734c2…b3f8
0x34b655…2a6f
6 touches
3 conflicts
0x9a7a0eb0…f2b2
0x34b655…2a6f
6 touches
3 conflicts
0x2c7dca88…74fb
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
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 0xca70fa2c6f…e96a7e
Audit this contract →
← previous block·next block →recent activity