← previous blocknext block →recent activity
Analyzing
Block #101,892,846
15 transactions · 15 stateful · 2026-09-04 11:48:28 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,892,846 · 15 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
2w03w14w25w36w07w19w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
8 touches
6 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x626b9be5…9c3a
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
6 touches
3 conflicts
0xa7e3ddfa…f0c7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity