← previous blocknext block →recent activity
Analyzing
Block #102,250,084
24 transactions · 23 stateful · 2026-09-05 17:59:25 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,250,084 · 24 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
1w04w15w26w310w012w113w214w315w416w318w420w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0x9c088939…ddd7
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x9bff3222…a246
0x34b655…2a6f
8 touches
6 conflicts
0x79ec4509…1f61
0x34b655…2a6f
6 touches
3 conflicts
0x7fd951f1…fe49
0x34b655…2a6f
6 touches
3 conflicts
0x839d77a9…9a51
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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity