← previous blocknext block →recent activity
Analyzing
Block #101,894,242
13 transactions · 13 stateful · 2026-09-04 11:55:31 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,894,242 · 13 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
1w02w13w14w25w37w08w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xe8114298…585b
0x34b655…2a6f
8 touches
6 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0xbd949841…fe2a
0x34b655…2a6f
6 touches
3 conflicts
0xc4f2b9b5…8a71
0x34b655…2a6f
6 touches
3 conflicts
0xc7bb912f…ad41
0x34b655…2a6f
6 touches
3 conflicts
0xcf6b4333…6ed5
0x34b655…2a6f
6 touches
3 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
6 touches
3 conflicts
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity