← previous blocknext block →recent activity
Analyzing
Block #102,571,830
37 transactions · 25 stateful · 2026-09-06 21:10:04 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,571,830 · 37 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
3w04w15w27w08w110w011w118w219w321w222w325w427w528w630w133w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc4c2e618…7480
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0dbb4745…3b18
0x34b655…2a6f
6 touches
3 conflicts
0x4ee66471…90b5
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
21 conflicts on slot 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity