← previous blocknext block →recent activity
Analyzing
Block #102,493,699
17 transactions · 15 stateful · 2026-09-06 14:33:50 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,493,699 · 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
1w05w16w013w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76efc1cc…4488
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0deb5804…40c6
0x34b655…2a6f
2 touches
0 conflicts
0x13cb3693…f4df
0x34b655…2a6f
2 touches
0 conflicts
0x2611eca1…5766
0x34b655…2a6f
2 touches
0 conflicts
0x2875af52…ac41
0x34b655…2a6f
2 touches
0 conflicts
0x28c12006…72a3
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 0x76efc1cc59…644488
Audit this contract →
← previous block·next block →recent activity