← previous blocknext block →recent activity
Analyzing
Block #101,325,764
19 transactions · 18 stateful · 2026-09-02 12:15:30 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,325,764 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w08w19w212w113w315w417w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x19b75130…e50c
0x34b655…2a6f
4 touches
1 conflict
0x1fa1f2d8…6bb5
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xed903df2a7…046ea4
Audit this contract →
← previous block·next block →recent activity