← previous blocknext block →recent activity
Analyzing
Block #101,315,428
31 transactions · 27 stateful · 2026-09-02 11:23:30 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,315,428 · 31 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
1w03w04w06w17w18w09w010w111w212w013w214w115w216w123w327w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6ed3ab3c…cf22
0x34b655…2a6f
4 touches
1 conflict
0x7923dbc4…0322
0x34b655…2a6f
4 touches
1 conflict
0x88a0cc80…7230
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 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity