← previous blocknext block →recent activity
Analyzing
Block #103,212,342
24 transactions · 19 stateful · 2026-09-09 03:00:18 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,212,342 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w115w216w017w118w319w220w322w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x40035c43…216c
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0x5f40adf2…e754
0x34b655…2a6f
6 touches
3 conflicts
0x76a639da…08f7
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity