← previous blocknext block →recent activity
Analyzing
Block #102,153,162
16 transactions · 15 stateful · 2026-09-05 09:48:17 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,153,162 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247cfb80…cca8
0x34b655…2a6f
14 touches
21 conflicts
0x904fb3c2…4291
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
0x34b655…2a6f
6 touches
3 conflicts
0xae83b422…f868
0x34b655…2a6f
6 touches
3 conflicts
0x8a02d049…f481
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
21 conflicts on slot 0x247cfb80ae…c4cca8
Audit this contract →
← previous block·next block →recent activity