← previous blocknext block →recent activity
Analyzing
Block #101,662,994
11 transactions · 10 stateful · 2026-09-03 16:32:13 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,662,994 · 11 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
1w02w13w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x55a17fc0…dfb4
0x34b655…2a6f
4 touches
1 conflict
0x970667dd…fb66
0x34b655…2a6f
4 touches
1 conflict
0x20b1228b…2487
0x34b655…2a6f
2 touches
0 conflicts
0x2b7d52dc…0371
0x34b655…2a6f
2 touches
0 conflicts
0x325d8ae4…fac6
0x34b655…2a6f
2 touches
0 conflicts
0x4089d428…b018
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
1 conflict on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity