← previous blocknext block →recent activity
Analyzing
Block #101,662,582
17 transactions · 16 stateful · 2026-09-03 16:30:08 UTC
Parallelism
47/100
Blocked
63%
Avg conflicts / tx
1.41
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,662,582 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w49w410w511w612w714w015w116w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x980e8c5d…6387
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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
10 conflicts on slot 0x980e8c5dd0…cf6387
Audit this contract →
← previous block·next block →recent activity