← previous blocknext block →recent activity
Analyzing
Block #102,653,885
16 transactions · 16 stateful · 2026-09-07 04:04:48 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,653,885 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w011w112w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xdb8288e3…7979
0x34b655…2a6f
4 touches
1 conflict
0xdd6538fb…2b3f
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity