← previous blocknext block →recent activity
Analyzing
Block #101,663,329
22 transactions · 20 stateful · 2026-09-03 16:33:54 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,663,329 · 22 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
3w04w17w08w19w210w313w014w017w018w119w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xdd18ee05…d486
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x20b1228b…2487
0x34b655…2a6f
4 touches
1 conflict
0x60104451…9e49
0x34b655…2a6f
4 touches
1 conflict
0x630dc607…7cc8
0x34b655…2a6f
4 touches
1 conflict
0x694150e1…8d87
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity