← previous blocknext block →recent activity
Analyzing
Block #101,839,369
29 transactions · 26 stateful · 2026-09-04 07:19:21 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,839,369 · 29 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
1w02w05w16w18w213w315w417w525w027w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6446340…5dda
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xce2afb0d…94be
0x34b655…2a6f
6 touches
3 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0x5a545e00…31bd
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0xf6446340c2…265dda
Audit this contract →
← previous block·next block →recent activity