← previous blocknext block →recent activity
Analyzing
Block #101,842,161
19 transactions · 18 stateful · 2026-09-04 07:33:24 UTC
Parallelism
42/100
Blocked
56%
Avg conflicts / tx
1.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,842,161 · 19 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w17w28w310w412w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x521ca204…da49
0x34b655…2a6f
8 touches
6 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0x995dd5a8…ce9c
0x34b655…2a6f
6 touches
3 conflicts
0xe3d3422c…0308
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity