← previous blocknext block →recent activity
Analyzing
Block #102,742,654
22 transactions · 19 stateful · 2026-09-07 11:31:25 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,742,654 · 22 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
2w03w15w06w27w38w09w113w414w516w020w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xc95b691a…6761
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity