← previous blocknext block →recent activity
Analyzing
Block #101,894,950
14 transactions · 13 stateful · 2026-09-04 11:59:07 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,894,950 · 14 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
1w02w13w04w15w06w08w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x819d93e2…aa4a
0x34b655…2a6f
4 touches
1 conflict
0x25c0f8b5…4246
0x754704…b603
4 touches
1 conflict
0x8226c92c…ece7
0x754704…b603
4 touches
1 conflict
0xe4940a46…26a0
0x754704…b603
4 touches
1 conflict
0x3b9910a2…6177
0x99c7a7…8bf0
4 touches
1 conflict
0xd6d0e119…6a6a
0x99c7a7…8bf0
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xb654bd89…a83b
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 0x819d93e20c…1aaa4a
Audit this contract →
← previous block·next block →recent activity