← previous blocknext block →recent activity
Analyzing
Block #102,006,666
24 transactions · 20 stateful · 2026-09-04 21:25:49 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,006,666 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w29w310w411w012w117w519w121w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x240838f0…5b9e
0x34b655…2a6f
4 touches
1 conflict
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x5ad364dd…07df
0x34b655…2a6f
4 touches
1 conflict
0x65ff54af…aa01
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0xb3605e81…0296
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity