← previous blocknext block →recent activity
Analyzing
Block #102,268,738
17 transactions · 13 stateful · 2026-09-05 19:33:58 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,268,738 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w19w010w113w114w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x031120c7…5bf2
0x34b655…2a6f
4 touches
1 conflict
0x3bb0b210…5f8d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4ac4a2c2…2707
0x34b655…2a6f
4 touches
1 conflict
0x8b84e242…bb72
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfb682e7d…dde9
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
1 conflict on slot 0x031120c7ba…095bf2
Audit this contract →
← previous block·next block →recent activity