← previous blocknext block →recent activity
Analyzing
Block #102,068,816
24 transactions · 17 stateful · 2026-09-05 02:40:38 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,068,816 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w014w017w121w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa84f5de5…af11
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xadc848ee…5cb2
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0001
0x776059…1d8d
2 touches
0 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
3 conflicts on slot 0xa84f5de58e…4faf11
Audit this contract →
← previous block·next block →recent activity