← previous blocknext block →recent activity
Analyzing
Block #102,249,303
27 transactions · 23 stateful · 2026-09-05 17:55:28 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,249,303 · 27 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
2w03w04w05w06w17w09w110w214w115w316w418w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08399ab6…0057
0x34b655…2a6f
10 touches
10 conflicts
0xd56bf871…6dae
0x34b655…2a6f
6 touches
3 conflicts
0x744138db…a855
0x34b655…2a6f
6 touches
3 conflicts
0xb4df814c…dcf9
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0xb82f494f…db33
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 0x08399ab6e2…e00057
Audit this contract →
← previous block·next block →recent activity