← previous blocknext block →recent activity
Analyzing
Block #102,373,503
22 transactions · 19 stateful · 2026-09-06 04:24:44 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,373,503 · 22 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
4w05w17w28w312w015w116w218w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x05989745…a42b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xefc390ec…2988
0x34b655…2a6f
4 touches
1 conflict
0x9feec606…4ad5
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity