← previous blocknext block →recent activity
Analyzing
Block #101,922,780
14 transactions · 14 stateful · 2026-09-04 14:20:11 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,922,780 · 14 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
1w02w14w25w36w210w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x626b9be5…9c3a
0x34b655…2a6f
6 touches
3 conflicts
0x66d0c4a4…add3
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x007e9b3e…0eb6
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
3 conflicts on slot 0x626b9be52d…f29c3a
Audit this contract →
← previous block·next block →recent activity