← previous blocknext block →recent activity
Analyzing
Block #101,301,534
23 transactions · 21 stateful · 2026-09-02 10:13:35 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,301,534 · 23 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
1w02w03w05w16w27w18w29w010w114w115w216w318w119w320w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e135144…4167
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x3a3097d7…2ab6
0x1b6862…e19c
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 0x4e135144ab…684167
Audit this contract →
← previous block·next block →recent activity