← previous blocknext block →recent activity
Analyzing
Block #102,306,640
13 transactions · 13 stateful · 2026-09-05 22:45:59 UTC
Parallelism
46/100
Blocked
54%
Avg conflicts / tx
1.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,306,640 · 13 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
2w03w14w25w36w49w510w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x850dd907…2612
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe108b282…58b3
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
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
10 conflicts on slot 0x850dd9079f…4c2612
Audit this contract →
← previous block·next block →recent activity