← previous blocknext block →recent activity
Analyzing
Block #101,937,406
15 transactions · 12 stateful · 2026-09-04 15:34:28 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,937,406 · 15 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
1w02w13w24w19w210w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf5fe80…1ffc
0x34b655…2a6f
8 touches
6 conflicts
0xd9c469b1…caf0
0x34b655…2a6f
6 touches
3 conflicts
0xf2a70d6a…8385
0x350035…7777
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x1d1b78c2…9055
0x34b655…2a6f
2 touches
0 conflicts
0x1d26d55a…aacd
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
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
6 conflicts on slot 0xfaf5fe80ab…a71ffc
Audit this contract →
← previous block·next block →recent activity