← previous blocknext block →recent activity
Analyzing
Block #102,209,259
14 transactions · 14 stateful · 2026-09-05 14:32:39 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,209,259 · 14 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
3w06w07w18w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x3d408a46…8a53
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb9d6e96a…c0fb
0xe52b14…7230
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 0x00f245ce7e…641e10
Audit this contract →
← previous block·next block →recent activity