← previous blocknext block →recent activity
Analyzing
Block #102,191,319
25 transactions · 22 stateful · 2026-09-05 13:01:42 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,191,319 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w010w111w212w317w418w523w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b94f7c…2a9b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x487bd835…8723
0x34b655…2a6f
8 touches
6 conflicts
0x2f018a76…73b7
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xcaf046db…fe6e
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0x20b94f7c91…602a9b
Audit this contract →
← previous block·next block →recent activity