← previous blocknext block →recent activity
Analyzing
Block #101,967,848
20 transactions · 14 stateful · 2026-09-04 18:08:52 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,967,848 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w011w112w217w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe41a834d…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x62bb20db…431e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x45364cf9…65d3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x4188cc5f…2d2e
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 0xe41a834d63…51a88a
Audit this contract →
← previous block·next block →recent activity