← previous blocknext block →recent activity
Analyzing
Block #101,967,016
19 transactions · 17 stateful · 2026-09-04 18:04:40 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,967,016 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w010w212w013w114w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ff8f69b…f7ab
0x34b655…2a6f
6 touches
3 conflicts
0x94789504…4524
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x343df2b7…a241
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
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 0x5ff8f69b9c…69f7ab
Audit this contract →
← previous block·next block →recent activity