← previous blocknext block →recent activity
Analyzing
Block #102,549,928
25 transactions · 23 stateful · 2026-09-06 19:19:02 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,549,928 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w37w38w49w510w612w113w215w420w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0x928a938f…9498
0x065c9d…c394
5 touches
3 conflicts
0x997ccc40…4dfd
0x3bd359…433a
4 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
4 touches
1 conflict
0x0b552eae…fbd9
0x754704…b603
4 touches
1 conflict
0x13477596…b14c
0x754704…b603
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity