← previous blocknext block →recent activity
Analyzing
Block #102,482,750
17 transactions · 15 stateful · 2026-09-06 13:38:14 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,482,750 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w08w111w113w214w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6413ac…b27f
0x34b655…2a6f
6 touches
3 conflicts
0x0d2d23d3…8a3a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xdd6413ac9e…44b27f
Audit this contract →
← previous block·next block →recent activity