← previous blocknext block →recent activity
Analyzing
Block #102,110,105
15 transactions · 14 stateful · 2026-09-05 06:10:04 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,110,105 · 15 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
2w03w14w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0xa769c16e…ef75
0x34b655…2a6f
4 touches
1 conflict
0x5363946e…9f68
0x34b655…2a6f
2 touches
0 conflicts
0x68055fa2…229e
0x34b655…2a6f
2 touches
0 conflicts
0x79ec4509…1f61
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity