← previous blocknext block →recent activity
Analyzing
Block #101,666,302
15 transactions · 15 stateful · 2026-09-03 16:48:51 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,666,302 · 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
1w02w13w27w29w211w312w414w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5850dde5…44f6
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x70f836c8…cf6d
0x34b655…2a6f
6 touches
3 conflicts
0x873d44c4…d4c4
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x2b093939…9087
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0x5850dde53d…fb44f6
Audit this contract →
← previous block·next block →recent activity