← previous blocknext block →recent activity
Analyzing
Block #102,744,499
16 transactions · 9 stateful · 2026-09-07 11:40:42 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,744,499 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0x998a77c2…67c6
0x34b655…2a6f
3 touches
1 conflict
0x17091c69…e7f3
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x9c9675f7…a878
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6426
0x34b655…2a6f
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity