← previous blocknext block →recent activity
Analyzing
Block #101,968,179
19 transactions · 15 stateful · 2026-09-04 18:10:33 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,968,179 · 19 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
2w09w110w212w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5932b264…0246
0x34b655…2a6f
6 touches
3 conflicts
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
2 touches
0 conflicts
0xbb6e8844…f073
0x37db7f…ec7b
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 0x5932b26470…520246
Audit this contract →
← previous block·next block →recent activity