← previous blocknext block →recent activity
Analyzing
Block #102,116,279
18 transactions · 17 stateful · 2026-09-05 06:41:23 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,116,279 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w312w413w414w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
8 touches
6 conflicts
0x6a8c9bff…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x5f630bff…7abb
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity