← previous blocknext block →recent activity
Analyzing
Block #101,315,388
19 transactions · 17 stateful · 2026-09-02 11:23:17 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,315,388 · 19 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
1w03w05w08w19w210w111w213w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ce19b50…f20f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x54904061…47a2
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf2dc7074…4491
0x34b655…2a6f
6 touches
3 conflicts
0x324f1810…6c8b
0x34b655…2a6f
6 touches
3 conflicts
0x08d78521…1726
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 0x5ce19b502b…21f20f
Audit this contract →
← previous block·next block →recent activity