← previous blocknext block →recent activity
Analyzing
Block #102,670,583
14 transactions · 12 stateful · 2026-09-07 05:28:48 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,670,583 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w19w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2d23d3…8a3a
0x34b655…2a6f
4 touches
1 conflict
0x9301a8d9…fdad
0x34b655…2a6f
4 touches
1 conflict
0xa1bfcd69…07cf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd88688e3…30a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0d2d23d3eb…148a3a
Audit this contract →
← previous block·next block →recent activity