← previous blocknext block →recent activity
Analyzing
Block #102,105,014
23 transactions · 19 stateful · 2026-09-05 05:44:16 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,105,014 · 23 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
1w03w16w210w011w116w217w318w419w420w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd4b3690…9a33
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x62bb20db…431e
0x34b655…2a6f
8 touches
6 conflicts
0x6c28863e…840e
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0x7b67f6cf…0aab
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
10 conflicts on slot 0xbd4b369019…ba9a33
Audit this contract →
← previous block·next block →recent activity