← previous blocknext block →recent activity
Analyzing
Block #101,986,663
30 transactions · 24 stateful · 2026-09-04 19:44:17 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,986,663 · 30 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
1w05w18w09w111w012w115w116w218w325w026w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc2cb2646…c7d6
0xd32edf…ff58
5 touches
3 conflicts
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity