← previous blocknext block →recent activity
Analyzing
Block #102,249,116
16 transactions · 15 stateful · 2026-09-05 17:54:31 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,249,116 · 16 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
2w03w04w17w010w111w212w313w414w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91726e1e…9f91
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9d017b93…8081
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0x820d7282…6c34
0x34b655…2a6f
6 touches
3 conflicts
0x5da92df7…74b5
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
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
10 conflicts on slot 0x91726e1eea…7c9f91
Audit this contract →
← previous block·next block →recent activity