← previous blocknext block →recent activity
Analyzing
Block #101,967,374
21 transactions · 19 stateful · 2026-09-04 18:06:28 UTC
Parallelism
76/100
Blocked
26%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,967,374 · 21 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
1w04w08w09w112w114w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x3d408a46…8a53
0x34b655…2a6f
8 touches
6 conflicts
0x2483afb0…443e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0000
0x24bf77…906e
4 touches
1 conflict
0x00000000…0003
0x24bf77…906e
4 touches
1 conflict
0x9ac96109…3059
0x405b63…7777
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity