← previous blocknext block →recent activity
Analyzing
Block #101,315,595
21 transactions · 19 stateful · 2026-09-02 11:24:20 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,315,595 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w28w011w112w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x8571fbdb…345a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x45622c74…1cf8
0x34b655…2a6f
4 touches
1 conflict
0x10abefc9…c9bc
0x34ae4d…3fc5
2 touches
0 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 conflicts
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 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity