← previous blocknext block →recent activity
Analyzing
Block #100,093,739
40 transactions · 36 stateful · 2026-08-29 04:52:16 UTC
Parallelism
70/100
Blocked
72%
Avg conflicts / tx
2.38
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,093,739 · 40 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w08w018w119w220w124w427w133w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1616198…661f
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x61571888…b392
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6cc500b1…55cd
0x34b655…2a6f
10 touches
10 conflicts
0x1b60b708…5b4b
0x2b46c0…1669
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
10 touches
10 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
36 conflicts on slot 0xa16161980f…11661f
Audit this contract →
← previous block·next block →recent activity