← previous blocknext block →recent activity
Analyzing
Block #101,663,041
20 transactions · 19 stateful · 2026-09-03 16:32:27 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,663,041 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w19w210w211w312w314w415w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
6 touches
3 conflicts
0xdd7be8ea…0288
0x34b655…2a6f
6 touches
3 conflicts
0x23b66ab4…6161
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x31102221…9952
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
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 0xf7772b4910…d2fc12
Audit this contract →
← previous block·next block →recent activity